Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 002492a0c309b17b6888b8bb9c029bfd13ced9d942b2d423c3af2aa249926953

Tx prefix hash: 9f6ccc06613d20cf69da5111078f596ad64d6abbda1fadddb733ac6c136afd5f
Tx public key: 1ae2eb7d24ad2a7d35dfc6c8bf6e8d9c2acc1c569c2057a58f739187ff98ff81
Timestamp: 1749002444 Timestamp [UCT]: 2025-06-04 02:00:44 Age [y:d:h:m:s]: 00:160:18:33:53
Block: 1297463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112573 RingCT/type: yes/0
Extra: 011ae2eb7d24ad2a7d35dfc6c8bf6e8d9c2acc1c569c2057a58f739187ff98ff81021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aca81a732d4ce1ba8237a9c0b8d297c23dc7bdd8e3ed6ca4f532e6ccb348b4d 0.600000000000 1784982 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": 1297473, "vin": [ { "gen": { "height": 1297463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aca81a732d4ce1ba8237a9c0b8d297c23dc7bdd8e3ed6ca4f532e6ccb348b4d" } } ], "extra": [ 1, 26, 226, 235, 125, 36, 173, 42, 125, 53, 223, 198, 200, 191, 110, 141, 156, 42, 204, 28, 86, 156, 32, 87, 165, 143, 115, 145, 135, 255, 152, 255, 129, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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