Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd57f7589a0c201d704df14fd70b09954be1fd653a8cbc2847d7c1dc56a7960e

Tx prefix hash: 233bd63125188e96027d140f0d895eb20174fd9b272e2e975d607d76069dab6e
Tx public key: 4a29ea872a1a2d01378afdbb282068319e147f496eed3a7be456a2f3a450dc34
Timestamp: 1738220785 Timestamp [UCT]: 2025-01-30 07:06:25 Age [y:d:h:m:s]: 00:320:14:26:01
Block: 1208196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226923 RingCT/type: yes/0
Extra: 014a29ea872a1a2d01378afdbb282068319e147f496eed3a7be456a2f3a450dc34021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d84d5a18fdb12b9a7ec4b3a0594f212651cfcaca0d196facbee0a49874b8f2 0.600000000000 1694925 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": 1208206, "vin": [ { "gen": { "height": 1208196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d84d5a18fdb12b9a7ec4b3a0594f212651cfcaca0d196facbee0a49874b8f2" } } ], "extra": [ 1, 74, 41, 234, 135, 42, 26, 45, 1, 55, 138, 253, 187, 40, 32, 104, 49, 158, 20, 127, 73, 110, 237, 58, 123, 228, 86, 162, 243, 164, 80, 220, 52, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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