Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fa24107bc6500717f91e017ada703403aede97abdc4fea5b57db7de6c2274ef

Tx prefix hash: d8b8fbd8241043d56c653f2de97c755109911af9ddd1930b8fed80809380d81f
Tx public key: 707ac5a2c26889d62039ac4f7441d19a163d7acae0916e3f8c5bcd17509a378c
Timestamp: 1764377035 Timestamp [UTC]: 2025-11-29 00:43:55 Age [y:d:h:m:s]: 00:353:04:59:43
Block: 1422335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257842 RingCT/type: yes/0
Extra: 01707ac5a2c26889d62039ac4f7441d19a163d7acae0916e3f8c5bcd17509a378c021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 28ca11dd084f9feaafea1af9c3db04a652ba61b39e2020ee2d27242c72deea9d 0.000600000000 1910900 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 dinastycoin-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": 1422345, "vin": [ { "gen": { "height": 1422335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28ca11dd084f9feaafea1af9c3db04a652ba61b39e2020ee2d27242c72deea9d" } } ], "extra": [ 1, 112, 122, 197, 162, 194, 104, 137, 214, 32, 57, 172, 79, 116, 65, 209, 154, 22, 61, 122, 202, 224, 145, 110, 63, 140, 91, 205, 23, 80, 154, 55, 140, 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): devel-2026-02-02-6303d2a (1.2) | monero version: