Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eeb27a90eb3e4c634941d6350505eecb97b46c49daa9b10d608831af6f8acf6

Tx prefix hash: 009ed3251f17ba9363417c60561f6b7eccd02a7b12aef8802df3575b8d9bd1b7
Tx public key: 8293247ad714a82e38aa5079bfd7512bf6cb3a63e18369233f4efa9de38d5708
Timestamp: 1705403848 Timestamp [UCT]: 2024-01-16 11:17:28 Age [y:d:h:m:s]: 01:321:20:05:22
Block: 936531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488867 RingCT/type: yes/0
Extra: 018293247ad714a82e38aa5079bfd7512bf6cb3a63e18369233f4efa9de38d570802110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98303f3f1aa44942fe05159bab1c20a8711e93af9766f00fd5d2c2ae2361123d 0.600000000000 1394559 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": 936541, "vin": [ { "gen": { "height": 936531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98303f3f1aa44942fe05159bab1c20a8711e93af9766f00fd5d2c2ae2361123d" } } ], "extra": [ 1, 130, 147, 36, 122, 215, 20, 168, 46, 56, 170, 80, 121, 191, 215, 81, 43, 246, 203, 58, 99, 225, 131, 105, 35, 63, 78, 250, 157, 227, 141, 87, 8, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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