Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc05189c1d02db36af8311c840d9e73bc7e33c0271c45ecf6f0a871d7f9477bd

Tx prefix hash: ab4c3ed335df14cc70b13e8252856a736bbedfdf99e869ef6f914fc63644ba12
Tx public key: 6a5f8d74f4240e411e7a27f4971fe32955ab0943403faa97c73e56323b0e419f
Timestamp: 1736588934 Timestamp [UCT]: 2025-01-11 09:48:54 Age [y:d:h:m:s]: 00:060:05:44:36
Block: 1194952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42827 RingCT/type: yes/0
Extra: 016a5f8d74f4240e411e7a27f4971fe32955ab0943403faa97c73e56323b0e419f021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5dda94a7cf247827a36e61b5c47ce5806734daa9507d92f301071845ea04c6f 0.600000000000 1681533 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": 1194962, "vin": [ { "gen": { "height": 1194952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5dda94a7cf247827a36e61b5c47ce5806734daa9507d92f301071845ea04c6f" } } ], "extra": [ 1, 106, 95, 141, 116, 244, 36, 14, 65, 30, 122, 39, 244, 151, 31, 227, 41, 85, 171, 9, 67, 64, 63, 170, 151, 199, 62, 86, 50, 59, 14, 65, 159, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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