Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c3e89e15cc3520b5057504d11e3b2bee5b25cda80db40b410c2b8033bde28cd

Tx prefix hash: 514811e29070ce50c7edef489cba93ff7680f5a97fb0066609909b01a3118116
Tx public key: 01cc55c07e852cb05868f9f6d16637b500a2530f0d4262ddd14cb9ef4f081c29
Timestamp: 1715694662 Timestamp [UCT]: 2024-05-14 13:51:02 Age [y:d:h:m:s]: 01:014:18:07:39
Block: 1021873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271476 RingCT/type: yes/0
Extra: 0101cc55c07e852cb05868f9f6d16637b500a2530f0d4262ddd14cb9ef4f081c29021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354e8bf9e1e7c7528ced55b7b58dc15f2ae83a0a640de5c7441a8769143b1d14 0.600000000000 1486308 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": 1021883, "vin": [ { "gen": { "height": 1021873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354e8bf9e1e7c7528ced55b7b58dc15f2ae83a0a640de5c7441a8769143b1d14" } } ], "extra": [ 1, 1, 204, 85, 192, 126, 133, 44, 176, 88, 104, 249, 246, 209, 102, 55, 181, 0, 162, 83, 15, 13, 66, 98, 221, 209, 76, 185, 239, 79, 8, 28, 41, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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