Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee2ce8db3eb995c9b534761dccc13704f1783640a33e5cf1b35878b5c8b70150

Tx prefix hash: 4aebfcf975321c4135b9f76cecbe20690bbfbbe91787147013d1bcd9f7c6e7cd
Tx public key: a8f0c8f9f0b726d1c070688ef050d1a8b23c878594880a92ad51ea21693ea9d9
Timestamp: 1723334645 Timestamp [UCT]: 2024-08-11 00:04:05 Age [y:d:h:m:s]: 00:240:08:52:06
Block: 1085205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171662 RingCT/type: yes/0
Extra: 01a8f0c8f9f0b726d1c070688ef050d1a8b23c878594880a92ad51ea21693ea9d9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 013dbad741c5e0442151804608760ff77f8b136a5c1424c2e737a293335ac11a 0.600000000000 1559736 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": 1085215, "vin": [ { "gen": { "height": 1085205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "013dbad741c5e0442151804608760ff77f8b136a5c1424c2e737a293335ac11a" } } ], "extra": [ 1, 168, 240, 200, 249, 240, 183, 38, 209, 192, 112, 104, 142, 240, 80, 209, 168, 178, 60, 135, 133, 148, 136, 10, 146, 173, 81, 234, 33, 105, 62, 169, 217, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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