Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47d4b15da7229e26acbeae64f93a4beb8e66c7ca745cb609ed6bbf89e8c681fc

Tx prefix hash: d1cf9c65020232a6c5a8ce419231d2a84ddb01c90a4dc75167bf0a7de1fc65fd
Tx public key: 71616eb02d9b9bdd619f9864e9ecb8b93fe5af4329ddf72805e0eda3c11ad83e
Timestamp: 1747904021 Timestamp [UCT]: 2025-05-22 08:53:41 Age [y:d:h:m:s]: 00:251:21:51:21
Block: 1288355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177650 RingCT/type: yes/0
Extra: 0171616eb02d9b9bdd619f9864e9ecb8b93fe5af4329ddf72805e0eda3c11ad83e0211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1707d820d200bdaacd0506172323e81ff01087ef2cd5f8377cb6abb36edd6d8 0.600000000000 1775822 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": 1288365, "vin": [ { "gen": { "height": 1288355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1707d820d200bdaacd0506172323e81ff01087ef2cd5f8377cb6abb36edd6d8" } } ], "extra": [ 1, 113, 97, 110, 176, 45, 155, 155, 221, 97, 159, 152, 100, 233, 236, 184, 185, 63, 229, 175, 67, 41, 221, 247, 40, 5, 224, 237, 163, 193, 26, 216, 62, 2, 17, 0, 0, 0, 7, 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