Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bde6835b1ea1b0d0da09dd8a4b92c423d3895f30ab3515253944af135572f146

Tx prefix hash: 5bee83954b45c4599d3b62d7622cee8ab141543fe5f250ce9252382aa5288b9b
Tx public key: fb9a856f2aed6b45e28841eae92e51e063dc1d45fa7e84eaba1d17fb485a7b5c
Timestamp: 1708698044 Timestamp [UCT]: 2024-02-23 14:20:44 Age [y:d:h:m:s]: 01:020:04:44:05
Block: 963859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275461 RingCT/type: yes/0
Extra: 01fb9a856f2aed6b45e28841eae92e51e063dc1d45fa7e84eaba1d17fb485a7b5c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab0a00e0c721c422f1333ab3c62332a2a717ae451d599be8f620a771a9b752b1 0.600000000000 1423586 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": 963869, "vin": [ { "gen": { "height": 963859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab0a00e0c721c422f1333ab3c62332a2a717ae451d599be8f620a771a9b752b1" } } ], "extra": [ 1, 251, 154, 133, 111, 42, 237, 107, 69, 226, 136, 65, 234, 233, 46, 81, 224, 99, 220, 29, 69, 250, 126, 132, 234, 186, 29, 23, 251, 72, 90, 123, 92, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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