Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19ca1f62b4be54b717318a61d2a88c75da55ef6c1f831571183a6689d6f2401a

Tx prefix hash: b09bb4f73102f0773c59552a269c67d7afebc9ce90f94fd174b70f436360604b
Tx public key: c7f53d28680c1f6f7b0123c8b0b5a3cec126c38924cc7a159f9ace6bea281415
Timestamp: 1755942028 Timestamp [UCT]: 2025-08-23 09:40:28 Age [y:d:h:m:s]: 00:095:06:15:58
Block: 1352608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68036 RingCT/type: yes/0
Extra: 01c7f53d28680c1f6f7b0123c8b0b5a3cec126c38924cc7a159f9ace6bea2814150211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe1b25de2930be8038f30320aa9c65aceedb3eb48adcf62b651693c9bb5e228 0.600000000000 1840575 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": 1352618, "vin": [ { "gen": { "height": 1352608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe1b25de2930be8038f30320aa9c65aceedb3eb48adcf62b651693c9bb5e228" } } ], "extra": [ 1, 199, 245, 61, 40, 104, 12, 31, 111, 123, 1, 35, 200, 176, 181, 163, 206, 193, 38, 195, 137, 36, 204, 122, 21, 159, 154, 206, 107, 234, 40, 20, 21, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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