Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9029c85d20727404c58445bbbf4dbb07a289f893a1b04294a9e22dd77c7e31ba

Tx prefix hash: 9f02642fdc85a0bd1d6700d95da6a0180a502081e6e26b8ea0e416a62f930dfd
Tx public key: ff85f4a7355c82ec487d65b5fc341b6780362f47952c03883e9f006e538873d4
Timestamp: 1764474832 Timestamp [UCT]: 2025-11-30 03:53:52 Age [y:d:h:m:s]: 00:004:09:40:47
Block: 1423147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3168 RingCT/type: yes/0
Extra: 01ff85f4a7355c82ec487d65b5fc341b6780362f47952c03883e9f006e538873d4021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 392b184b27af19c88ede609258cc5d1597cc506a3a3fcf4994ed9234a18053c1 0.600000000000 1911750 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": 1423157, "vin": [ { "gen": { "height": 1423147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "392b184b27af19c88ede609258cc5d1597cc506a3a3fcf4994ed9234a18053c1" } } ], "extra": [ 1, 255, 133, 244, 167, 53, 92, 130, 236, 72, 125, 101, 181, 252, 52, 27, 103, 128, 54, 47, 71, 149, 44, 3, 136, 62, 159, 0, 110, 83, 136, 115, 212, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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