Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64629eca4eaa50a8c83ea9d83510e9d2527a1cf9858c22b76c4092ab193b544c

Tx prefix hash: df1dfefa87d2acac23de8cdb6ead971dc855d22ff65733c4a6fea577d1348143
Tx public key: 8ebe15532c374a4e10330d52ab8923e7b451e1aa5ab0c2295b5eba3d3e377e6b
Timestamp: 1707575460 Timestamp [UCT]: 2024-02-10 14:31:00 Age [y:d:h:m:s]: 01:094:00:39:24
Block: 954537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328294 RingCT/type: yes/0
Extra: 018ebe15532c374a4e10330d52ab8923e7b451e1aa5ab0c2295b5eba3d3e377e6b0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 376a4226de5d2fcd69ac5d41ebfec423ab708d3459d00abfdb878206ae8975e8 0.600000000000 1413817 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": 954547, "vin": [ { "gen": { "height": 954537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "376a4226de5d2fcd69ac5d41ebfec423ab708d3459d00abfdb878206ae8975e8" } } ], "extra": [ 1, 142, 190, 21, 83, 44, 55, 74, 78, 16, 51, 13, 82, 171, 137, 35, 231, 180, 81, 225, 170, 90, 176, 194, 41, 91, 94, 186, 61, 62, 55, 126, 107, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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