Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8f97b64ff7ea63e8e7ba92b522b2c1a89788a83323de368f5fa93efa9bcabb6

Tx prefix hash: 8f58a7fb138a8ba8409720160b1cafe81330f466edf848fae07d239fa39755d3
Tx public key: 5b5db48e9afe63d99b4fd5feeb6cc4700900e74e1ecdc40f1ada0abbcbf2b841
Timestamp: 1722041818 Timestamp [UCT]: 2024-07-27 00:56:58 Age [y:d:h:m:s]: 00:325:00:19:42
Block: 1074478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232134 RingCT/type: yes/0
Extra: 015b5db48e9afe63d99b4fd5feeb6cc4700900e74e1ecdc40f1ada0abbcbf2b84102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe9b36aaba2b5b35cdab548110fe32696b9f2eb0c5a06228facf04580ca19f4b 0.600000000000 1546991 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": 1074488, "vin": [ { "gen": { "height": 1074478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe9b36aaba2b5b35cdab548110fe32696b9f2eb0c5a06228facf04580ca19f4b" } } ], "extra": [ 1, 91, 93, 180, 142, 154, 254, 99, 217, 155, 79, 213, 254, 235, 108, 196, 112, 9, 0, 231, 78, 30, 205, 196, 15, 26, 218, 10, 187, 203, 242, 184, 65, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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