Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c17d567da8c77782cea7e66030093026658b6edccd471f8c63daed6b356a5a14

Tx prefix hash: 43baff76b1775b0627ecbb166ac22df5f18cf1ecd34e44e854f1d7d63aa7c77d
Tx public key: 20e4f59d10b4ca5ec5175a533ccd6da79e292b68d22a83b48ff1a0b5bfaf4ce6
Timestamp: 1763472076 Timestamp [UCT]: 2025-11-18 13:21:16 Age [y:d:h:m:s]: 00:075:23:53:18
Block: 1414829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54237 RingCT/type: yes/0
Extra: 0120e4f59d10b4ca5ec5175a533ccd6da79e292b68d22a83b48ff1a0b5bfaf4ce602110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30fd8d2102a97b2b6ec106ab30d5d2c25bc7992918954e9ea9763581bd218850 0.600000000000 1903322 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": 1414839, "vin": [ { "gen": { "height": 1414829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30fd8d2102a97b2b6ec106ab30d5d2c25bc7992918954e9ea9763581bd218850" } } ], "extra": [ 1, 32, 228, 245, 157, 16, 180, 202, 94, 197, 23, 90, 83, 60, 205, 109, 167, 158, 41, 43, 104, 210, 42, 131, 180, 143, 241, 160, 181, 191, 175, 76, 230, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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