Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f02d033127d3e56a28cfce07dfa7b05b552df3cef7b8de18db9556c8f7d393

Tx prefix hash: 1e12be1dc35f87bc05b7d9d0bea9c4a09cc40d57bfad0902164d584d983649ec
Tx public key: 30dc23ef8f9f82dfa75293a3254b7be381ce59821a7c93b321e6f62319d9b641
Timestamp: 1696528326 Timestamp [UCT]: 2023-10-05 17:52:06 Age [y:d:h:m:s]: 01:181:16:16:35
Block: 863166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390893 RingCT/type: yes/0
Extra: 0130dc23ef8f9f82dfa75293a3254b7be381ce59821a7c93b321e6f62319d9b64102110000000975e3f0e9000000000000000000

1 output(s) for total of 0.847174280000 dcy

stealth address amount amount idx
00: 69bf3c029dd9d2f242f5b67bf9f6490d19e99252117adc8a5f4e43a7ce1c65a0 0.847174280000 1317614 of 0

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": 863176, "vin": [ { "gen": { "height": 863166 } } ], "vout": [ { "amount": 847174280, "target": { "key": "69bf3c029dd9d2f242f5b67bf9f6490d19e99252117adc8a5f4e43a7ce1c65a0" } } ], "extra": [ 1, 48, 220, 35, 239, 143, 159, 130, 223, 167, 82, 147, 163, 37, 75, 123, 227, 129, 206, 89, 130, 26, 124, 147, 179, 33, 230, 246, 35, 25, 217, 182, 65, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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