Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08be1b8357cd1a36ac449a92035e4b1f74cf6f127cdb3f2b750682d7c5592e9e

Tx prefix hash: 468fe82965f9cd874cead7a745e505d681bdaf85bef692e64bc27d50a4fb68c7
Tx public key: 2b3aafc16e9b64a3d7d6e80ba2bcfb057612dc8ce610af542908d3f8f6ed5c65
Timestamp: 1727439405 Timestamp [UCT]: 2024-09-27 12:16:45 Age [y:d:h:m:s]: 00:117:11:03:07
Block: 1119231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83940 RingCT/type: yes/0
Extra: 012b3aafc16e9b64a3d7d6e80ba2bcfb057612dc8ce610af542908d3f8f6ed5c6502110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 165dc94eb0ecc7ba483ec5697032c400521f38bdc9e33cec7d9f00279a0582bc 0.600000000000 1600712 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": 1119241, "vin": [ { "gen": { "height": 1119231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "165dc94eb0ecc7ba483ec5697032c400521f38bdc9e33cec7d9f00279a0582bc" } } ], "extra": [ 1, 43, 58, 175, 193, 110, 155, 100, 163, 215, 214, 232, 11, 162, 188, 251, 5, 118, 18, 220, 140, 230, 16, 175, 84, 41, 8, 211, 248, 246, 237, 92, 101, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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