Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b20a3f587dcbdaf00b0c4db10fb8f92da1032e0a8d8f260cc0109b064b449dd8

Tx prefix hash: 08338aa200887a31c491e4f90764ce724838eba89a9d7738bddae245162e431f
Tx public key: f0e4e4a2a5ecf4ed5bcc72c7b1abfca0c87b783b61a2a9f0608904f721c037f2
Timestamp: 1754673289 Timestamp [UCT]: 2025-08-08 17:14:49 Age [y:d:h:m:s]: 00:056:01:52:39
Block: 1342946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39117 RingCT/type: yes/0
Extra: 01f0e4e4a2a5ecf4ed5bcc72c7b1abfca0c87b783b61a2a9f0608904f721c037f2021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77422b1543358c751246fc0ce5647e3983e863d6d3d0f9b9f7b9dfd2723af7b4 0.600000000000 1830781 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": 1342956, "vin": [ { "gen": { "height": 1342946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77422b1543358c751246fc0ce5647e3983e863d6d3d0f9b9f7b9dfd2723af7b4" } } ], "extra": [ 1, 240, 228, 228, 162, 165, 236, 244, 237, 91, 204, 114, 199, 177, 171, 252, 160, 200, 123, 120, 59, 97, 162, 169, 240, 96, 137, 4, 247, 33, 192, 55, 242, 2, 17, 0, 0, 0, 1, 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