Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e312a9670e12c9c05f8bf86d752e5001e676ee56d8842f565c73f5b938d0c89

Tx prefix hash: 1a96446ac4b2dcf145d431eea8331ed4d9d64099e124a8bc56ff439918783a3e
Tx public key: a6aec03e1097d9bef657b81f669a514a79acce4f8b520e2d8ff574c45759a9e2
Timestamp: 1712644567 Timestamp [UCT]: 2024-04-09 06:36:07 Age [y:d:h:m:s]: 01:205:18:43:19
Block: 996549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405762 RingCT/type: yes/0
Extra: 01a6aec03e1097d9bef657b81f669a514a79acce4f8b520e2d8ff574c45759a9e202110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5529c6292d0b854ec6d3dcf255d7e938583ded2642b7a71763c97e8193e887e3 0.600000000000 1456971 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": 996559, "vin": [ { "gen": { "height": 996549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5529c6292d0b854ec6d3dcf255d7e938583ded2642b7a71763c97e8193e887e3" } } ], "extra": [ 1, 166, 174, 192, 62, 16, 151, 217, 190, 246, 87, 184, 31, 102, 154, 81, 74, 121, 172, 206, 79, 139, 82, 14, 45, 143, 245, 116, 196, 87, 89, 169, 226, 2, 17, 0, 0, 0, 10, 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