Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f47da7773e71b73e940b18c92c42fb7c1cf740d5a89a919b2285add374b48c

Tx prefix hash: 32f5eca828d3ddd4905ef57d515408924988d38d3863ead14d02cd15e1d506de
Tx public key: f16bb464ccc6d7a5456b79b72d353882e84b3887d8c529f646f754befcbdf5a8
Timestamp: 1762932198 Timestamp [UCT]: 2025-11-12 07:23:18 Age [y:d:h:m:s]: 00:015:23:35:37
Block: 1410355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11447 RingCT/type: yes/0
Extra: 01f16bb464ccc6d7a5456b79b72d353882e84b3887d8c529f646f754befcbdf5a8021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a88e0c26440fce6cc351e76f3990a2dfd70752692b7e080abf5369f52a702ea 0.600000000000 1898806 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": 1410365, "vin": [ { "gen": { "height": 1410355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a88e0c26440fce6cc351e76f3990a2dfd70752692b7e080abf5369f52a702ea" } } ], "extra": [ 1, 241, 107, 180, 100, 204, 198, 215, 165, 69, 107, 121, 183, 45, 53, 56, 130, 232, 75, 56, 135, 216, 197, 41, 246, 70, 247, 84, 190, 252, 189, 245, 168, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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