Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2a9ca0959e58ab1d54a0f22e8447b835caeeacb712ae28aad932a82017be022

Tx prefix hash: b2d9624ffaa641c48343da7d14f1136b6b0577e01de0fb641a887ff18d5b7be3
Tx public key: 4a60fe16e998fdf72ceaf1ada07fcdb8dcb52cdf86a59bc2dfee4acc1af64769
Timestamp: 1658216294 Timestamp [UCT]: 2022-07-19 07:38:14 Age [y:d:h:m:s]: 02:210:07:08:59
Block: 546989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 671448 RingCT/type: yes/0
Extra: 014a60fe16e998fdf72ceaf1ada07fcdb8dcb52cdf86a59bc2dfee4acc1af64769021100000002d3fcec30000000000000000000

1 output(s) for total of 9.453628107000 dcy

stealth address amount amount idx
00: dfb28c1453308731bfcfddec80e2ffa34a3db9f452d1bd1207a5e6a4d718213b 9.453628107000 978070 of 0

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": 546999, "vin": [ { "gen": { "height": 546989 } } ], "vout": [ { "amount": 9453628107, "target": { "key": "dfb28c1453308731bfcfddec80e2ffa34a3db9f452d1bd1207a5e6a4d718213b" } } ], "extra": [ 1, 74, 96, 254, 22, 233, 152, 253, 247, 44, 234, 241, 173, 160, 127, 205, 184, 220, 181, 44, 223, 134, 165, 155, 194, 223, 238, 74, 204, 26, 246, 71, 105, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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