Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c899a179d952efbbcbd03be47db5e54315c3134764cd893e9ba8471302ce88f

Tx prefix hash: b8cb14555ea2451925e94d6a5875fec22ff72e8d76a2a247b71086db872b6428
Tx public key: 35cf6e6218a4a2b828cd19ed12714b5817a0c6a23afc519ec720fa919d62a089
Timestamp: 1726824400 Timestamp [UCT]: 2024-09-20 09:26:40 Age [y:d:h:m:s]: 00:111:18:27:01
Block: 1114129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79920 RingCT/type: yes/0
Extra: 0135cf6e6218a4a2b828cd19ed12714b5817a0c6a23afc519ec720fa919d62a089021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4be817427dcc4f938c09c2a99751b9eaa91e4472b05249c68e5fd97bce4985b6 0.600000000000 1593928 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": 1114139, "vin": [ { "gen": { "height": 1114129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4be817427dcc4f938c09c2a99751b9eaa91e4472b05249c68e5fd97bce4985b6" } } ], "extra": [ 1, 53, 207, 110, 98, 24, 164, 162, 184, 40, 205, 25, 237, 18, 113, 75, 88, 23, 160, 198, 162, 58, 252, 81, 158, 199, 32, 250, 145, 157, 98, 160, 137, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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