Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9a9e84f507cf7fdce2668fa084d5680efc47679c4dce1d83be1827f586b1876

Tx prefix hash: c736fffc3274c1e528f62ef2fb6d8983e1c2946f5cdeecb3c722a3f1812373e6
Tx public key: 9e51b6b2f610b70bbf48058a788be49074fe4da4931d5a3ddb59f871c64a1d14
Timestamp: 1732690967 Timestamp [UCT]: 2024-11-27 07:02:47 Age [y:d:h:m:s]: 00:167:01:46:17
Block: 1162669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119245 RingCT/type: yes/0
Extra: 019e51b6b2f610b70bbf48058a788be49074fe4da4931d5a3ddb59f871c64a1d14021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06475912fb326da28080d415f42317699aaef59d00788e129eeced9e1a232466 0.600000000000 1648326 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": 1162679, "vin": [ { "gen": { "height": 1162669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06475912fb326da28080d415f42317699aaef59d00788e129eeced9e1a232466" } } ], "extra": [ 1, 158, 81, 182, 178, 246, 16, 183, 11, 191, 72, 5, 138, 120, 139, 228, 144, 116, 254, 77, 164, 147, 29, 90, 61, 219, 89, 248, 113, 198, 74, 29, 20, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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