Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68e84f9f58c82b4ad17dc27f0c7f2fb94982e6743e7922c54aa048adcdbcd181

Tx prefix hash: d09309380cfd81dc5f80fefda88905ad5bc4216a9d27482f90f6d4b108d47e96
Tx public key: 8bba2eb8935689500e29b5b9b6a9ab663de1ac2dd6a89c4748c7637118525e42
Timestamp: 1746675921 Timestamp [UCT]: 2025-05-08 03:45:21 Age [y:d:h:m:s]: 00:194:06:02:09
Block: 1278179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136545 RingCT/type: yes/0
Extra: 018bba2eb8935689500e29b5b9b6a9ab663de1ac2dd6a89c4748c7637118525e420211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f9c4ba1265af251a05ba0831bdd4801a4f041b41eb158cf7c766ba0bc5bc2b9 0.600000000000 1765544 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": 1278189, "vin": [ { "gen": { "height": 1278179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f9c4ba1265af251a05ba0831bdd4801a4f041b41eb158cf7c766ba0bc5bc2b9" } } ], "extra": [ 1, 139, 186, 46, 184, 147, 86, 137, 80, 14, 41, 181, 185, 182, 169, 171, 102, 61, 225, 172, 45, 214, 168, 156, 71, 72, 199, 99, 113, 24, 82, 94, 66, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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