Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396faa45f32a736c4a75d819b48645d6cfb68fa4124d65e38487c4caec94e27c

Tx prefix hash: 17c8bc4525185a4d2b308df0674da25d7efcc38cdd3b783b6c45fdb678cc56ce
Tx public key: 262afddbf16439100e53b762c69d0b24f94d4dc13d7cdb03f20c9c0247dc9e4e
Timestamp: 1710056224 Timestamp [UCT]: 2024-03-10 07:37:04 Age [y:d:h:m:s]: 01:024:16:21:59
Block: 975129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278625 RingCT/type: yes/0
Extra: 01262afddbf16439100e53b762c69d0b24f94d4dc13d7cdb03f20c9c0247dc9e4e02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63e1fdbb0132607a419cec503003db79d3f79fe587e0aa21010bcdb404441d89 0.600000000000 1435100 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": 975139, "vin": [ { "gen": { "height": 975129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63e1fdbb0132607a419cec503003db79d3f79fe587e0aa21010bcdb404441d89" } } ], "extra": [ 1, 38, 42, 253, 219, 241, 100, 57, 16, 14, 83, 183, 98, 198, 157, 11, 36, 249, 77, 77, 193, 61, 124, 219, 3, 242, 12, 156, 2, 71, 220, 158, 78, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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