Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30406cd6d606af5b7ecb84bf7129a9c5bbf346ed60f1c87272510432df1cd767

Tx prefix hash: 241c2a5e9b5c5fb4a880f85a607f69a948c3a79b597fd904d1f4a0795e97d8b2
Tx public key: cecfe8820ce6a179bc0965e5e90e1ef81ec80ca96d75c2f74d5cdd7a98b59797
Timestamp: 1715018493 Timestamp [UCT]: 2024-05-06 18:01:33 Age [y:d:h:m:s]: 00:191:15:04:40
Block: 1016261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137162 RingCT/type: yes/0
Extra: 01cecfe8820ce6a179bc0965e5e90e1ef81ec80ca96d75c2f74d5cdd7a98b597970211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0e4d843a189219c691413af703d88e1934e82fbd17a72c7da5e9f8a9749485c 0.600000000000 1479792 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": 1016271, "vin": [ { "gen": { "height": 1016261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e4d843a189219c691413af703d88e1934e82fbd17a72c7da5e9f8a9749485c" } } ], "extra": [ 1, 206, 207, 232, 130, 12, 230, 161, 121, 188, 9, 101, 229, 233, 14, 30, 248, 30, 200, 12, 169, 109, 117, 194, 247, 77, 92, 221, 122, 152, 181, 151, 151, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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