Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e20edd3a10d6f09abf5974d0b4922fdaf108a6ae8951e0eae99dc417311e1d8

Tx prefix hash: bf34441dbe4da02ed84e07a7e6b7ae2f17d4d987c54fee78526cfcad1aa458ae
Tx public key: 49071ffb3b9fe691330383c0a4539a5f71a230c064d1b55f12a26ee059dea074
Timestamp: 1759612520 Timestamp [UCT]: 2025-10-04 21:15:20 Age [y:d:h:m:s]: 00:003:06:21:01
Block: 1382840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2336 RingCT/type: yes/0
Extra: 0149071ffb3b9fe691330383c0a4539a5f71a230c064d1b55f12a26ee059dea074021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64175563038644e596196c3a30eea19b3625aabc74039a40221fcc044b81b231 0.600000000000 1870983 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": 1382850, "vin": [ { "gen": { "height": 1382840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64175563038644e596196c3a30eea19b3625aabc74039a40221fcc044b81b231" } } ], "extra": [ 1, 73, 7, 31, 251, 59, 159, 230, 145, 51, 3, 131, 192, 164, 83, 154, 95, 113, 162, 48, 192, 100, 209, 181, 95, 18, 162, 110, 224, 89, 222, 160, 116, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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