Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bbd0b9268f81135c111e11bea3ffc0ed9179fc3510426a03191d105f500e8ce

Tx prefix hash: 7a00e160e5365e44ad82d54801e125c9cfa714e57dfd84893c8c819ceaebda83
Tx public key: fd29d0016aa0001ae0e365f273e18ec8f87bfcc1adc1581a34e22c236bc4d1d2
Timestamp: 1720540480 Timestamp [UCT]: 2024-07-09 15:54:40 Age [y:d:h:m:s]: 00:282:14:00:20
Block: 1062041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201903 RingCT/type: yes/0
Extra: 01fd29d0016aa0001ae0e365f273e18ec8f87bfcc1adc1581a34e22c236bc4d1d202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb81f074a3a79e865ff4710f7bf15ef13e8d840d60837fcc1daba517b8bab211 0.600000000000 1532542 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": 1062051, "vin": [ { "gen": { "height": 1062041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb81f074a3a79e865ff4710f7bf15ef13e8d840d60837fcc1daba517b8bab211" } } ], "extra": [ 1, 253, 41, 208, 1, 106, 160, 0, 26, 224, 227, 101, 242, 115, 225, 142, 200, 248, 123, 252, 193, 173, 193, 88, 26, 52, 226, 44, 35, 107, 196, 209, 210, 2, 17, 0, 0, 0, 5, 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