Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f448c2eb9b2ea722d13c1073d0ec4dfa1c554f6238bde49b5ab1213a3f9f428

Tx prefix hash: 9561b85c8808bf62f5147ddfd7a7c8d6cdc7ca493b9b6bf1fc8d47b9f71ad2cd
Tx public key: 6ddca7fa56d169745eccbe2efcdb6925116f8841ce289edb758b77def43072ce
Timestamp: 1733735700 Timestamp [UCT]: 2024-12-09 09:15:00 Age [y:d:h:m:s]: 00:101:20:19:39
Block: 1171334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72584 RingCT/type: yes/0
Extra: 016ddca7fa56d169745eccbe2efcdb6925116f8841ce289edb758b77def43072ce021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0cd9aee4fc18f299ed5a39aaad201c2c26e7548628d560b9a031ae2efa1adf3 0.600000000000 1657075 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": 1171344, "vin": [ { "gen": { "height": 1171334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0cd9aee4fc18f299ed5a39aaad201c2c26e7548628d560b9a031ae2efa1adf3" } } ], "extra": [ 1, 109, 220, 167, 250, 86, 209, 105, 116, 94, 204, 190, 46, 252, 219, 105, 37, 17, 111, 136, 65, 206, 40, 158, 219, 117, 139, 119, 222, 244, 48, 114, 206, 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