Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c9c9bb6c7698ef90326ff5474dd67f7afe2deae97e9a7a3655d1e8705038af1

Tx prefix hash: c336bd467750260295c23ae5a2b61e617195832405a552d992279d7091b82f59
Tx public key: a5a6b48e76888a42d030f0015be19cc7c787dfe40a370332d581c96e1da4f595
Timestamp: 1717265239 Timestamp [UCT]: 2024-06-01 18:07:19 Age [y:d:h:m:s]: 01:162:02:42:47
Block: 1034891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374435 RingCT/type: yes/0
Extra: 01a5a6b48e76888a42d030f0015be19cc7c787dfe40a370332d581c96e1da4f595021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 676dc4d5d50a228434491482db6b29b7b087da244c05b584c6e8207b46a0c7d0 0.600000000000 1503410 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": 1034901, "vin": [ { "gen": { "height": 1034891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "676dc4d5d50a228434491482db6b29b7b087da244c05b584c6e8207b46a0c7d0" } } ], "extra": [ 1, 165, 166, 180, 142, 118, 136, 138, 66, 208, 48, 240, 1, 91, 225, 156, 199, 199, 135, 223, 228, 10, 55, 3, 50, 213, 129, 201, 110, 29, 164, 245, 149, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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