Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02ea953e11dafac8ba18d0eb8e8e5c815728175282b77a45bf7bcd2b925d9a6f

Tx prefix hash: 2b4b1db0afa6466d0a28ded84b2f88bc0100e7f6c0e9788c1e2e3d7036d4aae9
Tx public key: 70c549a93d3f6f39c1b233bd7b5c4b4208ebdb3e08a04ad424c650d06808f9c1
Timestamp: 1789531247 Timestamp [UTC]: 2026-09-16 04:00:47 Age [y:d:h:m:s]: 00:062:19:28:21
Block: 1636464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 44258 RingCT/type: yes/0
Extra: 0170c549a93d3f6f39c1b233bd7b5c4b4208ebdb3e08a04ad424c650d06808f9c1

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 683128275809661062c4f66614de3ca4f9d157a9a10bb43cf8cfa616b6d5ddae 0.000600000000 2126494 of 15 <13>

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": 1636474, "vin": [ { "gen": { "height": 1636464 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "683128275809661062c4f66614de3ca4f9d157a9a10bb43cf8cfa616b6d5ddae", "view_tag": "13" } } } ], "extra": [ 1, 112, 197, 73, 169, 61, 63, 111, 57, 193, 178, 51, 189, 123, 92, 75, 66, 8, 235, 219, 62, 8, 160, 74, 212, 36, 198, 80, 208, 104, 8, 249, 193 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: