Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 454ec5f3bf1e75cede5c94b930301ab2fbdac605c36f6a2f0104e5c2b821aebb

Tx prefix hash: 1e2ea6f33797fcf5dd4db73966535f0c132ddf40958dcbf4f61799207943241a
Tx public key: a17c3f00186ada5c66626fca5adc469afdc960bc41d9f0dd76a553ae55af7d1f
Timestamp: 1738223842 Timestamp [UCT]: 2025-01-30 07:57:22 Age [y:d:h:m:s]: 00:042:22:08:39
Block: 1208216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30711 RingCT/type: yes/0
Extra: 01a17c3f00186ada5c66626fca5adc469afdc960bc41d9f0dd76a553ae55af7d1f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7012f729112f7b86170b24c4a25a820e1833632575e7e21c9f5734612c3361c3 0.600000000000 1694947 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": 1208226, "vin": [ { "gen": { "height": 1208216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7012f729112f7b86170b24c4a25a820e1833632575e7e21c9f5734612c3361c3" } } ], "extra": [ 1, 161, 124, 63, 0, 24, 106, 218, 92, 102, 98, 111, 202, 90, 220, 70, 154, 253, 201, 96, 188, 65, 217, 240, 221, 118, 165, 83, 174, 85, 175, 125, 31, 2, 17, 0, 0, 0, 4, 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