Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91b92f44ee745f57c16bdc90f525720333d71c82a6a0a43878fbfcb30edf7a8a

Tx prefix hash: f9df023c2931bb3994805df3765d6e470faf8491798d99fcc1cec84c951b69e8
Tx public key: f6e0acbe04bacd3fb63a4c6996f93d0d704d3f7d9747fd083accccfe40934349
Timestamp: 1761297338 Timestamp [UTC]: 2025-10-24 09:15:38 Age [y:d:h:m:s]: 01:028:09:28:44
Block: 1396826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286668 RingCT/type: yes/0
Extra: 01f6e0acbe04bacd3fb63a4c6996f93d0d704d3f7d9747fd083accccfe40934349021100000006e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 14a2a7716e3eb4e9a72f6eff05929533f59141b73f73223c2fd0dd441a221fa8 0.000600000000 1885113 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": 1396836, "vin": [ { "gen": { "height": 1396826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14a2a7716e3eb4e9a72f6eff05929533f59141b73f73223c2fd0dd441a221fa8" } } ], "extra": [ 1, 246, 224, 172, 190, 4, 186, 205, 63, 182, 58, 76, 105, 150, 249, 61, 13, 112, 77, 63, 125, 151, 71, 253, 8, 58, 204, 204, 254, 64, 147, 67, 73, 2, 17, 0, 0, 0, 6, 228, 220, 144, 9, 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: