Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ef72ebd0f81a943d98834c04ae5c396775e445a79731f95398333a8ecc6afc

Tx prefix hash: fc2d73a94e99eaa3dec99b8b97744014ad472c46775e1d3b16f2f098e687b233
Tx public key: 97c42f26c95925b8a15184d1e59ef30a946f1cc3824eae2ef306160cf6abef94
Timestamp: 1737630097 Timestamp [UCT]: 2025-01-23 11:01:37 Age [y:d:h:m:s]: 00:050:08:16:06
Block: 1203514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35813 RingCT/type: yes/0
Extra: 0197c42f26c95925b8a15184d1e59ef30a946f1cc3824eae2ef306160cf6abef940211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9e5e92ec4328e1a20d50e30916ff6b598a10fe524ebece495a4320538bb13b0 0.600000000000 1690191 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": 1203524, "vin": [ { "gen": { "height": 1203514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9e5e92ec4328e1a20d50e30916ff6b598a10fe524ebece495a4320538bb13b0" } } ], "extra": [ 1, 151, 196, 47, 38, 201, 89, 37, 184, 161, 81, 132, 209, 229, 158, 243, 10, 148, 111, 28, 195, 130, 78, 174, 46, 243, 6, 22, 12, 246, 171, 239, 148, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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