Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae33f63c7393ee7d30d8d066267eb5d9064db82ff3cfc70965a70f850da8feb

Tx prefix hash: 65c7db46f3c2eac34d9028204d53d162983f8368633b9a5777ae84822ae64cf3
Tx public key: 6b84d7138926b861e804554569d97554e7bdc1d70ae7f33f2bdced73f312de0b
Timestamp: 1754469460 Timestamp [UCT]: 2025-08-06 08:37:40 Age [y:d:h:m:s]: 00:060:10:49:00
Block: 1341356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42148 RingCT/type: yes/0
Extra: 016b84d7138926b861e804554569d97554e7bdc1d70ae7f33f2bdced73f312de0b021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da3876a3b6388b9f55aed9cd4d45cce4fb6e6a385b9ec75236fed33d9ffa0523 0.600000000000 1829181 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": 1341366, "vin": [ { "gen": { "height": 1341356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da3876a3b6388b9f55aed9cd4d45cce4fb6e6a385b9ec75236fed33d9ffa0523" } } ], "extra": [ 1, 107, 132, 215, 19, 137, 38, 184, 97, 232, 4, 85, 69, 105, 217, 117, 84, 231, 189, 193, 215, 10, 231, 243, 63, 43, 220, 237, 115, 243, 18, 222, 11, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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