Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0374500f1fdc1cbbe768e342f6329e6641fe1210fc0a53f335a3b5d3d301342

Tx prefix hash: efb7506adad072b33cf708a607de4d8acf126abfc11fb2c2d5d7fa89c10b161e
Tx public key: 8e5a33175ab1d0c2c1da3c879fda5a098e700643708f72a74974846cbc82c36f
Timestamp: 1708272644 Timestamp [UCT]: 2024-02-18 16:10:44 Age [y:d:h:m:s]: 01:073:13:30:44
Block: 960331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313613 RingCT/type: yes/0
Extra: 018e5a33175ab1d0c2c1da3c879fda5a098e700643708f72a74974846cbc82c36f02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39b13440a1c62f120cc2511cad844b6df765ec86e60b39262f0b27bdd26fdbc7 0.600000000000 1419894 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": 960341, "vin": [ { "gen": { "height": 960331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39b13440a1c62f120cc2511cad844b6df765ec86e60b39262f0b27bdd26fdbc7" } } ], "extra": [ 1, 142, 90, 51, 23, 90, 177, 208, 194, 193, 218, 60, 135, 159, 218, 90, 9, 142, 112, 6, 67, 112, 143, 114, 167, 73, 116, 132, 108, 188, 130, 195, 111, 2, 17, 0, 0, 0, 7, 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