Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6cc3ea0e9f5aef5ed947a441fb85f363eefbbb2b548cd17699793520f3747ab

Tx prefix hash: c0934bfaaf60f2f0a6872e1510c89ac5f52343ad25aeef3a35f104cd5ab9b2f8
Tx public key: e8af5eaece6d3c1331adb91e505a76d876ddbe984eddfb02c96af935acf06ab9
Timestamp: 1749381308 Timestamp [UCT]: 2025-06-08 11:15:08 Age [y:d:h:m:s]: 00:166:04:40:08
Block: 1300594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116449 RingCT/type: yes/0
Extra: 01e8af5eaece6d3c1331adb91e505a76d876ddbe984eddfb02c96af935acf06ab9021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25e456ac12c23df303c206df7ccf186d29f8637b482177cc40af41cbc90b8325 0.600000000000 1788143 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": 1300604, "vin": [ { "gen": { "height": 1300594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25e456ac12c23df303c206df7ccf186d29f8637b482177cc40af41cbc90b8325" } } ], "extra": [ 1, 232, 175, 94, 174, 206, 109, 60, 19, 49, 173, 185, 30, 80, 90, 118, 216, 118, 221, 190, 152, 78, 221, 251, 2, 201, 106, 249, 53, 172, 240, 106, 185, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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