Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f67d232b799a5f985c978dc237b53ca648b0ab90b8b967ef2c57208c0b69e930

Tx prefix hash: c45d65865d5871793612afe7d1add5746ad27319998548b2ba92b342f977c86c
Tx public key: afc5853cd1fa774d0f03b0046f768462537080a7c67b621d05d7589f9bff4fe6
Timestamp: 1694900120 Timestamp [UCT]: 2023-09-16 21:35:20 Age [y:d:h:m:s]: 01:251:08:11:43
Block: 849657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440759 RingCT/type: yes/0
Extra: 01afc5853cd1fa774d0f03b0046f768462537080a7c67b621d05d7589f9bff4fe6021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.939147284000 dcy

stealth address amount amount idx
00: 3da8e18a1794eef863c5a4ce710d05e64e16f843f26149f4bd7c10636ba8a5ff 0.939147284000 1303331 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 849667, "vin": [ { "gen": { "height": 849657 } } ], "vout": [ { "amount": 939147284, "target": { "key": "3da8e18a1794eef863c5a4ce710d05e64e16f843f26149f4bd7c10636ba8a5ff" } } ], "extra": [ 1, 175, 197, 133, 60, 209, 250, 119, 77, 15, 3, 176, 4, 111, 118, 132, 98, 83, 112, 128, 167, 198, 123, 98, 29, 5, 215, 88, 159, 155, 255, 79, 230, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8