Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b83c7212bdcb2e9705a6132fd70e7296001e9ba2230d24520f032930b2237c

Tx prefix hash: c5bc57d11546f2b146699b8e8a3d526a30d69354e2bbeefa69092bc3d0cf7aa8
Tx public key: 0bc23b0adaa2bd05ac4ae2d5e34735be2f5c5772f97dcc1a1b2fc429bb527a51
Timestamp: 1719420319 Timestamp [UCT]: 2024-06-26 16:45:19 Age [y:d:h:m:s]: 00:236:06:36:24
Block: 1052744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168776 RingCT/type: yes/0
Extra: 010bc23b0adaa2bd05ac4ae2d5e34735be2f5c5772f97dcc1a1b2fc429bb527a5102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25fff739f08b1730067271b3c0051087003abefc24c0e52080ad76a0db8ab655 0.600000000000 1523077 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": 1052754, "vin": [ { "gen": { "height": 1052744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25fff739f08b1730067271b3c0051087003abefc24c0e52080ad76a0db8ab655" } } ], "extra": [ 1, 11, 194, 59, 10, 218, 162, 189, 5, 172, 74, 226, 213, 227, 71, 53, 190, 47, 92, 87, 114, 249, 125, 204, 26, 27, 47, 196, 41, 187, 82, 122, 81, 2, 17, 0, 0, 0, 1, 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