Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bab0fcc3fff665957293705afd4e804cc9ae8480d299e4bf5cdb460f0f8b5b4

Tx prefix hash: e97dcb9dc79cf184d9f83b5f7d1a3f9ccad96f8d7289eb2465401b19790d7790
Tx public key: 496d7bce8fa9ffb9698358b1cc449d63af07cfd0d58bb836ab80e5a39c99015e
Timestamp: 1685569516 Timestamp [UCT]: 2023-05-31 21:45:16 Age [y:d:h:m:s]: 02:161:10:12:24
Block: 772361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 635154 RingCT/type: yes/0
Extra: 01496d7bce8fa9ffb9698358b1cc449d63af07cfd0d58bb836ab80e5a39c99015e02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.693743163000 dcy

stealth address amount amount idx
00: aa2d7f6a5a5663aa781e620e1e9d692dd257ec429d3b5785871e408e012e81ed 1.693743163000 1221762 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": 772371, "vin": [ { "gen": { "height": 772361 } } ], "vout": [ { "amount": 1693743163, "target": { "key": "aa2d7f6a5a5663aa781e620e1e9d692dd257ec429d3b5785871e408e012e81ed" } } ], "extra": [ 1, 73, 109, 123, 206, 143, 169, 255, 185, 105, 131, 88, 177, 204, 68, 157, 99, 175, 7, 207, 208, 213, 139, 184, 54, 171, 128, 229, 163, 156, 153, 1, 94, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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