Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62ca21f2ffcb1e9fb1a38dd00219833b9f9ca8c840034e99a5a4a000b836a6eb

Tx prefix hash: b86032c3509fde58407edf1c0ddac32142d7fb771f2d4e1e93e0ab86395c9f42
Tx public key: ba2906f7c7fe31d3bee6c77b9ee54996cf621da30ba2673601f407431f58d91d
Timestamp: 1712913513 Timestamp [UCT]: 2024-04-12 09:18:33 Age [y:d:h:m:s]: 01:018:13:57:36
Block: 998789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274250 RingCT/type: yes/0
Extra: 01ba2906f7c7fe31d3bee6c77b9ee54996cf621da30ba2673601f407431f58d91d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd69e286a0524c27b1ada9ad7d64d789bccd7999961de568ebf61ba5fef01e2b 0.600000000000 1459247 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": 998799, "vin": [ { "gen": { "height": 998789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd69e286a0524c27b1ada9ad7d64d789bccd7999961de568ebf61ba5fef01e2b" } } ], "extra": [ 1, 186, 41, 6, 247, 199, 254, 49, 211, 190, 230, 199, 123, 158, 229, 73, 150, 207, 98, 29, 163, 11, 162, 103, 54, 1, 244, 7, 67, 31, 88, 217, 29, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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