Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fef81a0a5ae0bacacd899b5aab46d60ae6eda90414093137a9a8a107243dbdf1

Tx prefix hash: 99fa9a23f9b28f1e25128df7c0fc2915c92795f58c1ba7c802b9d3f95c98e5fd
Tx public key: 6c6db3345b64a96c8740a11b632ef5775a3c84895289ce8d33efaeb4be6dd685
Timestamp: 1708768911 Timestamp [UCT]: 2024-02-24 10:01:51 Age [y:d:h:m:s]: 01:028:17:00:26
Block: 964454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281510 RingCT/type: yes/0
Extra: 016c6db3345b64a96c8740a11b632ef5775a3c84895289ce8d33efaeb4be6dd6850211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f456b0cfd7fefbf9050e5a0a650e51c43c371eb2d6141d039df5041313fe095 0.600000000000 1424193 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": 964464, "vin": [ { "gen": { "height": 964454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f456b0cfd7fefbf9050e5a0a650e51c43c371eb2d6141d039df5041313fe095" } } ], "extra": [ 1, 108, 109, 179, 52, 91, 100, 169, 108, 135, 64, 161, 27, 99, 46, 245, 119, 90, 60, 132, 137, 82, 137, 206, 141, 51, 239, 174, 180, 190, 109, 214, 133, 2, 17, 0, 0, 0, 2, 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