Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf493ea188a97ab5677f1837975b8de09512b3c4edd8b38aeb66310d3ca30c48

Tx prefix hash: a6901872dc3bf6a4fc2fa856fc11d1831a4d28b6c68197ed9835391650fe8ed8
Tx public key: ab96cb046ff868d5e65cf35f06d3b55e80a21634f946c32ce349f6c42b9eb3a0
Timestamp: 1697276613 Timestamp [UCT]: 2023-10-14 09:43:33 Age [y:d:h:m:s]: 01:178:02:12:25
Block: 869370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388318 RingCT/type: yes/0
Extra: 01ab96cb046ff868d5e65cf35f06d3b55e80a21634f946c32ce349f6c42b9eb3a002110000000775e3f0e9000000000000000000

1 output(s) for total of 0.808009237000 dcy

stealth address amount amount idx
00: 42e620e45ed4b6b63431e772d4adbec1769704675eed6fe2c759088fce09f271 0.808009237000 1324215 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": 869380, "vin": [ { "gen": { "height": 869370 } } ], "vout": [ { "amount": 808009237, "target": { "key": "42e620e45ed4b6b63431e772d4adbec1769704675eed6fe2c759088fce09f271" } } ], "extra": [ 1, 171, 150, 203, 4, 111, 248, 104, 213, 230, 92, 243, 95, 6, 211, 181, 94, 128, 162, 22, 52, 249, 70, 195, 44, 227, 73, 246, 196, 43, 158, 179, 160, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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