Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dd3f01711201cc9bb4f9594ab2a3a9f42af2f8cecea13c9ce2a483155aaf10e

Tx prefix hash: c87cdb1834510b9f0922de37dd325321f2e5c6a2f69c5a6367b1e76fcff05aef
Tx public key: cb07fe67244b17a599c64496e9ca9c006967c03db87383a4cdf16212d5b957a6
Timestamp: 1675263044 Timestamp [UCT]: 2023-02-01 14:50:44 Age [y:d:h:m:s]: 02:064:21:50:26
Block: 687536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 568017 RingCT/type: yes/0
Extra: 01cb07fe67244b17a599c64496e9ca9c006967c03db87383a4cdf16212d5b957a60211000000045029cbac000000000000000000

1 output(s) for total of 3.235249314000 dcy

stealth address amount amount idx
00: 942006c9663f4b6a4dfebf3afe5ee71a0757c90ed570973ee42b5e4f90023ed6 3.235249314000 1130111 of 0

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": 687546, "vin": [ { "gen": { "height": 687536 } } ], "vout": [ { "amount": 3235249314, "target": { "key": "942006c9663f4b6a4dfebf3afe5ee71a0757c90ed570973ee42b5e4f90023ed6" } } ], "extra": [ 1, 203, 7, 254, 103, 36, 75, 23, 165, 153, 198, 68, 150, 233, 202, 156, 0, 105, 103, 192, 61, 184, 115, 131, 164, 205, 241, 98, 18, 213, 185, 87, 166, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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