Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 702fda9dd9765a40b37714848c5f02dfe99de5e0bdd9f4b4140e1307d332b64e

Tx prefix hash: d5e3dfb30f1c25b09a986a538c302dda368c75b20e639df85428f90e37cc124b
Tx public key: f092c4b6252b8b7abfc758702096c6fe17ecf68c180d97605150c36ac876f4a9
Timestamp: 1754986370 Timestamp [UCT]: 2025-08-12 08:12:50 Age [y:d:h:m:s]: 00:098:10:43:52
Block: 1345335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69666 RingCT/type: yes/0
Extra: 01f092c4b6252b8b7abfc758702096c6fe17ecf68c180d97605150c36ac876f4a9021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81dadb3ee83a8bf96ea56ab78fde4c5f573bfb4a6b1676832c7503e7d7f373e4 0.600000000000 1833228 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": 1345345, "vin": [ { "gen": { "height": 1345335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81dadb3ee83a8bf96ea56ab78fde4c5f573bfb4a6b1676832c7503e7d7f373e4" } } ], "extra": [ 1, 240, 146, 196, 182, 37, 43, 139, 122, 191, 199, 88, 112, 32, 150, 198, 254, 23, 236, 246, 140, 24, 13, 151, 96, 81, 80, 195, 106, 200, 118, 244, 169, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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