Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6351f8ba788a828b3329faa42fd9ce225b62c412ebfc3186d041d58c756a924

Tx prefix hash: 74ba995efb963956e34d328e8f652d3c89062a9a862c12a9e2f90ad740e28ea1
Tx public key: 14742aa34f4b4eec3dcedae5c857fc9bdcd20b703f981eb0560099d229b4a5b7
Timestamp: 1738559132 Timestamp [UCT]: 2025-02-03 05:05:32 Age [y:d:h:m:s]: 00:291:19:16:28
Block: 1210976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206331 RingCT/type: yes/0
Extra: 0114742aa34f4b4eec3dcedae5c857fc9bdcd20b703f981eb0560099d229b4a5b70211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71e44f826335295d86f0dbca2d54fd6a6983ab5f251b361710e12289a1d46ca3 0.600000000000 1697731 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": 1210986, "vin": [ { "gen": { "height": 1210976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71e44f826335295d86f0dbca2d54fd6a6983ab5f251b361710e12289a1d46ca3" } } ], "extra": [ 1, 20, 116, 42, 163, 79, 75, 78, 236, 61, 206, 218, 229, 200, 87, 252, 155, 220, 210, 11, 112, 63, 152, 30, 176, 86, 0, 153, 210, 41, 180, 165, 183, 2, 17, 0, 0, 0, 7, 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