Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ae096d090e85975c79664b19f222531d7381a044657db70b22d130fb715dc9d

Tx prefix hash: 8da08c9ba7dc89f91052ac5b523f215e4a7b34dcab93c1e64acda0a80f02dd30
Tx public key: 9320e32e32e556219d50e65b49f593a59d15f272ade9dc9adf844935915a6c97
Timestamp: 1721289036 Timestamp [UCT]: 2024-07-18 07:50:36 Age [y:d:h:m:s]: 00:284:17:45:53
Block: 1068255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203436 RingCT/type: yes/0
Extra: 019320e32e32e556219d50e65b49f593a59d15f272ade9dc9adf844935915a6c9702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebc2944a65ea30da0e02739f4cdd02c22c38aa5038bd9481c28fd854cecf5749 0.600000000000 1539332 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": 1068265, "vin": [ { "gen": { "height": 1068255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebc2944a65ea30da0e02739f4cdd02c22c38aa5038bd9481c28fd854cecf5749" } } ], "extra": [ 1, 147, 32, 227, 46, 50, 229, 86, 33, 157, 80, 230, 91, 73, 245, 147, 165, 157, 21, 242, 114, 173, 233, 220, 154, 223, 132, 73, 53, 145, 90, 108, 151, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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