Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6454c06be4378aa5a21e2666a038e612ab7e8f4d234f5df13316239cc4c022a

Tx prefix hash: 0edd9a11d85ab4882715c9aa42536429aa5b1f59a324fc4f6477fd257ad55525
Tx public key: 95f60b11f6b8a86e84cfbd9bf3f110c5ee9231fde00794169de26f78f1a77e79
Timestamp: 1740670275 Timestamp [UCT]: 2025-02-27 15:31:15 Age [y:d:h:m:s]: 00:259:19:15:07
Block: 1228455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183438 RingCT/type: yes/0
Extra: 0195f60b11f6b8a86e84cfbd9bf3f110c5ee9231fde00794169de26f78f1a77e790211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 440d67dab330eff9eb343929e4fabf7e1c9c0200bf910be36b9080d8700e5fb3 0.600000000000 1715336 of 15

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": 1228465, "vin": [ { "gen": { "height": 1228455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "440d67dab330eff9eb343929e4fabf7e1c9c0200bf910be36b9080d8700e5fb3" } } ], "extra": [ 1, 149, 246, 11, 17, 246, 184, 168, 110, 132, 207, 189, 155, 243, 241, 16, 197, 238, 146, 49, 253, 224, 7, 148, 22, 157, 226, 111, 120, 241, 167, 126, 121, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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