Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c72e9fd602bd73402885936803865bc0e17478449c6eb22aa58b17e602786d85

Tx prefix hash: b9854c7c75da94ba38d5af240be1a92eafccd70bf61440f0fb4b48974680727e
Tx public key: 97f736a0b6a4e6d1c64b79a033d0c10f2d293da2d162e35ee0ef6ef160edd846
Timestamp: 1732257862 Timestamp [UCT]: 2024-11-22 06:44:22 Age [y:d:h:m:s]: 00:001:19:14:03
Block: 1159081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1298 RingCT/type: yes/0
Extra: 0197f736a0b6a4e6d1c64b79a033d0c10f2d293da2d162e35ee0ef6ef160edd846021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9a742ba0cc9be39a192a797fbd84439b96f00ffa44ffdd43f6d244730b1b619 0.600000000000 1644712 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": 1159091, "vin": [ { "gen": { "height": 1159081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9a742ba0cc9be39a192a797fbd84439b96f00ffa44ffdd43f6d244730b1b619" } } ], "extra": [ 1, 151, 247, 54, 160, 182, 164, 230, 209, 198, 75, 121, 160, 51, 208, 193, 15, 45, 41, 61, 162, 209, 98, 227, 94, 224, 239, 110, 241, 96, 237, 216, 70, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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