Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dcbe3b2fd955f6f159d9a597a70b0c60c640d5ff5a62862b35e44c43ebae79e

Tx prefix hash: a7003b088cbb13d2404a55ee12664a4c3a69cc612f626eabf31931204ed042ab
Tx public key: 3d4108b78cfb0b86e55130bb25cd9403f95d853e6822e532de672dd7e893e311
Timestamp: 1749774563 Timestamp [UCT]: 2025-06-13 00:29:23 Age [y:d:h:m:s]: 00:206:21:27:53
Block: 1303794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145684 RingCT/type: yes/0
Extra: 013d4108b78cfb0b86e55130bb25cd9403f95d853e6822e532de672dd7e893e311021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 916822f11649ff2d7cb76d0a067ad65482bbc01289b3454d8264ff1ec819324f 0.600000000000 1791379 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": 1303804, "vin": [ { "gen": { "height": 1303794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "916822f11649ff2d7cb76d0a067ad65482bbc01289b3454d8264ff1ec819324f" } } ], "extra": [ 1, 61, 65, 8, 183, 140, 251, 11, 134, 229, 81, 48, 187, 37, 205, 148, 3, 249, 93, 133, 62, 104, 34, 229, 50, 222, 103, 45, 215, 232, 147, 227, 17, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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