Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 009ad35840e8f967912b013ba0dc0b7422ee7f57a828398a86af8a0942efa01b

Tx prefix hash: 286098d1f20bce25a9475f5f51d696bc91b2c409897c347e09b2537571e8e750
Tx public key: b7b9763b9c4fb137fedb4d240c30b13aa09f37e467e6d3a2852180abe65d067f
Timestamp: 1710505117 Timestamp [UCT]: 2024-03-15 12:18:37 Age [y:d:h:m:s]: 01:241:12:19:46
Block: 978861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431304 RingCT/type: yes/0
Extra: 01b7b9763b9c4fb137fedb4d240c30b13aa09f37e467e6d3a2852180abe65d067f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b28515a1036ad05b0ccc38ca94f5b5dce3260c97aa0497d51efdd5b67e52af49 0.600000000000 1438890 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": 978871, "vin": [ { "gen": { "height": 978861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b28515a1036ad05b0ccc38ca94f5b5dce3260c97aa0497d51efdd5b67e52af49" } } ], "extra": [ 1, 183, 185, 118, 59, 156, 79, 177, 55, 254, 219, 77, 36, 12, 48, 177, 58, 160, 159, 55, 228, 103, 230, 211, 162, 133, 33, 128, 171, 230, 93, 6, 127, 2, 17, 0, 0, 0, 4, 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