Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0566cff1db399c5edb1b6b368da4de17ac06163a27cf2bdb1b68229081c4a66

Tx prefix hash: 1d67501b93cafc5ed8a61a1da1b2a5a8d22017cf7e796021cb15bf72567cf9dc
Tx public key: 0fa5c04363d60f080d34667badc9a040972b061c9280d0891d13aac9292acef8
Timestamp: 1710082512 Timestamp [UCT]: 2024-03-10 14:55:12 Age [y:d:h:m:s]: 00:305:12:11:47
Block: 975348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218681 RingCT/type: yes/0
Extra: 010fa5c04363d60f080d34667badc9a040972b061c9280d0891d13aac9292acef802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 697d65e54e472cec55aa78c9ab385547ea643e2cc047cfa9dcb95a5092de7a9b 0.600000000000 1435319 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": 975358, "vin": [ { "gen": { "height": 975348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "697d65e54e472cec55aa78c9ab385547ea643e2cc047cfa9dcb95a5092de7a9b" } } ], "extra": [ 1, 15, 165, 192, 67, 99, 214, 15, 8, 13, 52, 102, 123, 173, 201, 160, 64, 151, 43, 6, 28, 146, 128, 208, 137, 29, 19, 170, 201, 41, 42, 206, 248, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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