Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 239a75fbf29a32d2058b79018c659e63c9f836cb644888032f0a821e6228a092

Tx prefix hash: a9fa31f4f448b2dadf91cd2bc66614c3659bb9dd14f32a033bcbe9ba629f90ab
Tx public key: 4c9b4025e8c26f306ff9c51f0456c2cf135a9fc14fd02a247b7f265871d1fbcc
Timestamp: 1735377838 Timestamp [UCT]: 2024-12-28 09:23:58 Age [y:d:h:m:s]: 00:119:08:26:31
Block: 1184913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85115 RingCT/type: yes/0
Extra: 014c9b4025e8c26f306ff9c51f0456c2cf135a9fc14fd02a247b7f265871d1fbcc021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aca8d706550360a052f57096c3efcf58183085d0a5d668a16af04b74870c4275 0.600000000000 1671376 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": 1184923, "vin": [ { "gen": { "height": 1184913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aca8d706550360a052f57096c3efcf58183085d0a5d668a16af04b74870c4275" } } ], "extra": [ 1, 76, 155, 64, 37, 232, 194, 111, 48, 111, 249, 197, 31, 4, 86, 194, 207, 19, 90, 159, 193, 79, 208, 42, 36, 123, 127, 38, 88, 113, 209, 251, 204, 2, 17, 0, 0, 0, 6, 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