Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd337c1adf380f84035ddbb22d55ceab6e05c3894f1d07c7ec387acf5626aef8

Tx prefix hash: 071c9b10d4600f3d87b46bb43819cb059cd2b23518d4d603b7cdb8d7bfb498dc
Tx public key: a10640d114812c87b54ee66b3d23de21eba871f12fdf4acebe455b1745874453
Timestamp: 1705481155 Timestamp [UCT]: 2024-01-17 08:45:55 Age [y:d:h:m:s]: 01:078:07:16:40
Block: 937167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317068 RingCT/type: yes/0
Extra: 01a10640d114812c87b54ee66b3d23de21eba871f12fdf4acebe455b17458744530211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec6046d303dc8a3299ebd25f39e8a547bed2c8ea3cfe8a4a2b103c3e7c492f2 0.600000000000 1395211 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": 937177, "vin": [ { "gen": { "height": 937167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec6046d303dc8a3299ebd25f39e8a547bed2c8ea3cfe8a4a2b103c3e7c492f2" } } ], "extra": [ 1, 161, 6, 64, 209, 20, 129, 44, 135, 181, 78, 230, 107, 61, 35, 222, 33, 235, 168, 113, 241, 47, 223, 74, 206, 190, 69, 91, 23, 69, 135, 68, 83, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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