Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83ae124fbc4989c3e135b1d5e062d2b98cb588207960b3d842a7d1f378abc518

Tx prefix hash: 68073e10fa9f866b9f30aff20dbe2eb239534aafbc7c36bf2185686a8476164a
Tx public key: 68749293a1deef4a57ba4093407c2d4ea5d7e75aee68e721fdf94aac54c5da00
Timestamp: 1712006928 Timestamp [UCT]: 2024-04-01 21:28:48 Age [y:d:h:m:s]: 01:220:08:17:08
Block: 991258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416188 RingCT/type: yes/0
Extra: 0168749293a1deef4a57ba4093407c2d4ea5d7e75aee68e721fdf94aac54c5da000211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afb37fa3c3394562a4349045de18ea169196d07ba444c2af6c77b4ccbc64a091 0.600000000000 1451592 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": 991268, "vin": [ { "gen": { "height": 991258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afb37fa3c3394562a4349045de18ea169196d07ba444c2af6c77b4ccbc64a091" } } ], "extra": [ 1, 104, 116, 146, 147, 161, 222, 239, 74, 87, 186, 64, 147, 64, 124, 45, 78, 165, 215, 231, 90, 238, 104, 231, 33, 253, 249, 74, 172, 84, 197, 218, 0, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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