Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa3a5b71f07e436cd1891d75b5437ccbbf3b7ba3fc09acff6bc2a916a722852

Tx prefix hash: 5e501da7649097bd1d4a9e202c3e1e2a88ba9798071160905bfb8c55fbdc43a7
Tx public key: fdb6ec4cfc362fd3a855ca51866cd631e1de7110b67afbae1e5d4e0895ff0fc2
Timestamp: 1736554450 Timestamp [UCT]: 2025-01-11 00:14:10 Age [y:d:h:m:s]: 00:161:17:42:12
Block: 1194654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115266 RingCT/type: yes/0
Extra: 01fdb6ec4cfc362fd3a855ca51866cd631e1de7110b67afbae1e5d4e0895ff0fc20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9bd473e362ea8a56457874f19750370315cdb5494e30c8d3ac94e0222adbba0 0.600000000000 1681231 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": 1194664, "vin": [ { "gen": { "height": 1194654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9bd473e362ea8a56457874f19750370315cdb5494e30c8d3ac94e0222adbba0" } } ], "extra": [ 1, 253, 182, 236, 76, 252, 54, 47, 211, 168, 85, 202, 81, 134, 108, 214, 49, 225, 222, 113, 16, 182, 122, 251, 174, 30, 93, 78, 8, 149, 255, 15, 194, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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