Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 382dc7e82f20ca969f0f9d2c919b6afa272fff385bcb93e0301ee1c795980066

Tx prefix hash: 2c1d974a7ec12cef145e2f801e8ccff78b84b7c6a26cc3682fe0007269ddd422
Tx public key: a59ff8299e4c4836c53bc3fa1ee8669c91d0fb98ac0896bded1fca71c0ea6617
Timestamp: 1753328988 Timestamp [UCT]: 2025-07-24 03:49:48 Age [y:d:h:m:s]: 00:119:15:32:42
Block: 1332108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84333 RingCT/type: yes/0
Extra: 01a59ff8299e4c4836c53bc3fa1ee8669c91d0fb98ac0896bded1fca71c0ea6617021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b547b8b7608bfbaf2fbd6e31efc244d4083b4b4f9f9b4538741884ea87481efa 0.600000000000 1819905 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": 1332118, "vin": [ { "gen": { "height": 1332108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b547b8b7608bfbaf2fbd6e31efc244d4083b4b4f9f9b4538741884ea87481efa" } } ], "extra": [ 1, 165, 159, 248, 41, 158, 76, 72, 54, 197, 59, 195, 250, 30, 232, 102, 156, 145, 208, 251, 152, 172, 8, 150, 189, 237, 31, 202, 113, 192, 234, 102, 23, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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