Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b81e27a4654a9c50f829b298fae45a942bfd963b4b843c68fa1835815bea2e7

Tx prefix hash: 859e0e1bb0c5194a61e1b7f4da46aadb3739684fd0a38a7a02e8ca4b635fb3ce
Tx public key: dfe9e10fe1afd62f5ce2e65a4fc04f78d5f43175a57148a01ddf8474c00bec77
Timestamp: 1750274140 Timestamp [UCT]: 2025-06-18 19:15:40 Age [y:d:h:m:s]: 00:143:12:22:10
Block: 1307837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100381 RingCT/type: yes/0
Extra: 01dfe9e10fe1afd62f5ce2e65a4fc04f78d5f43175a57148a01ddf8474c00bec77021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb90232a3a8834e9a8a181f2432258b72804ee78bad2bc38007b460de5b6ebba 0.600000000000 1795448 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": 1307847, "vin": [ { "gen": { "height": 1307837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb90232a3a8834e9a8a181f2432258b72804ee78bad2bc38007b460de5b6ebba" } } ], "extra": [ 1, 223, 233, 225, 15, 225, 175, 214, 47, 92, 226, 230, 90, 79, 192, 79, 120, 213, 244, 49, 117, 165, 113, 72, 160, 29, 223, 132, 116, 192, 11, 236, 119, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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