Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 343cb073a439152aabea049a15ca0620c8e04a451bfaa88f70e1c03eb975f769

Tx prefix hash: 80d710361ea64e4dd5ca02efb38b795f4cd613aca9838a788b9c082e079720d6
Tx public key: b3102326b5c920be91e04f4852707296bf65bece4f2aa410e9eba20f65dc6ff6
Timestamp: 1711436063 Timestamp [UCT]: 2024-03-26 06:54:23 Age [y:d:h:m:s]: 01:023:07:48:15
Block: 986578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277633 RingCT/type: yes/0
Extra: 01b3102326b5c920be91e04f4852707296bf65bece4f2aa410e9eba20f65dc6ff602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80afbeaae72544d21c047ab9bc9849a46d1580ccf1a82b9b257ea17cb95fe227 0.600000000000 1446809 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": 986588, "vin": [ { "gen": { "height": 986578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80afbeaae72544d21c047ab9bc9849a46d1580ccf1a82b9b257ea17cb95fe227" } } ], "extra": [ 1, 179, 16, 35, 38, 181, 201, 32, 190, 145, 224, 79, 72, 82, 112, 114, 150, 191, 101, 190, 206, 79, 42, 164, 16, 233, 235, 162, 15, 101, 220, 111, 246, 2, 17, 0, 0, 0, 6, 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