Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f952ef2d514ba7aa036cabd4e8597d0001b92e2e5198bf23047fbddfdd26a76

Tx prefix hash: 4ae2216cd34b736b2bd4b35da95a4bbf640cf73ba4b3525c8b58748b07954459
Tx public key: 933bd14be1c1cf6da48296f07e7e37e75899bb0632b0b183ed99fc53a0c78f37
Timestamp: 1771244007 Timestamp [UTC]: 2026-02-16 12:13:27 Age [y:d:h:m:s]: 00:100:18:17:23
Block: 1479045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66083 RingCT/type: yes/0
Extra: 01933bd14be1c1cf6da48296f07e7e37e75899bb0632b0b183ed99fc53a0c78f37021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96f93fdaabe99b4c4972021a44070aec8fda42e3f7fe0081c64de239ac4f241d 0.000600000000 1968379 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": 1479055, "vin": [ { "gen": { "height": 1479045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96f93fdaabe99b4c4972021a44070aec8fda42e3f7fe0081c64de239ac4f241d" } } ], "extra": [ 1, 147, 59, 209, 75, 225, 193, 207, 109, 164, 130, 150, 240, 126, 126, 55, 231, 88, 153, 187, 6, 50, 176, 177, 131, 237, 153, 252, 83, 160, 199, 143, 55, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: