Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379c6adf9612b3fd9f03425f3077b17f07addcf394913964132160b0a4f90e2c

Tx prefix hash: 37384148e5d1835640cbd459e6d926fe0c7d77476de071b9f4f52c89b35e469d
Tx public key: a5d636fea464df9c4c232acbf52baa18c2805dd83614ad1de37a22b78af8b737
Timestamp: 1731695150 Timestamp [UCT]: 2024-11-15 18:25:50 Age [y:d:h:m:s]: 00:144:17:14:46
Block: 1154416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103267 RingCT/type: yes/0
Extra: 01a5d636fea464df9c4c232acbf52baa18c2805dd83614ad1de37a22b78af8b73702110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 039d76a6df1b68a2a700e40b7c3fe303da22804c4d190ce3b3aeb130fe55d6b0 0.600000000000 1640027 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": 1154426, "vin": [ { "gen": { "height": 1154416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "039d76a6df1b68a2a700e40b7c3fe303da22804c4d190ce3b3aeb130fe55d6b0" } } ], "extra": [ 1, 165, 214, 54, 254, 164, 100, 223, 156, 76, 35, 42, 203, 245, 43, 170, 24, 194, 128, 93, 216, 54, 20, 173, 29, 227, 122, 34, 183, 138, 248, 183, 55, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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