Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6cb9caa6d9b48a07082bb140db8129ddd62c22476bec19b9e293f93ff19570

Tx prefix hash: 018d2ebfe1cf6f20dbd067d07b6bd2dafc9a78530769377e9825d0c70db69e8d
Tx public key: 9c568509436428df9152d00d9ef6bbb98ffeeafd8dbe89195a7258fa5b2a8692
Timestamp: 1703782110 Timestamp [UCT]: 2023-12-28 16:48:30 Age [y:d:h:m:s]: 01:359:05:08:02
Block: 923104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515612 RingCT/type: yes/0
Extra: 019c568509436428df9152d00d9ef6bbb98ffeeafd8dbe89195a7258fa5b2a869202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e1b00f89262c23cdc054aa209ba3e6bc7c4c7d3ad547168f871eecf1b7b931a 0.600000000000 1380822 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": 923114, "vin": [ { "gen": { "height": 923104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e1b00f89262c23cdc054aa209ba3e6bc7c4c7d3ad547168f871eecf1b7b931a" } } ], "extra": [ 1, 156, 86, 133, 9, 67, 100, 40, 223, 145, 82, 208, 13, 158, 246, 187, 185, 143, 254, 234, 253, 141, 190, 137, 25, 90, 114, 88, 250, 91, 42, 134, 146, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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