Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0250b9b12942e1f31c3284d7cafe2c3a6c834376a25cf31c38b4449ed2d6ab

Tx prefix hash: 562ee28bb7b8890ecd92d5ef06e535c0933d930781618a131b46bf7a2b9eded5
Tx public key: 9df075a8d2dea23a1ad1c0e0638d134df4758822481c633f292752e55ce6e63b
Timestamp: 1783123421 Timestamp [UTC]: 2026-07-04 00:03:41 Age [y:d:h:m:s]: 00:140:18:31:16
Block: 1574117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 109377 RingCT/type: yes/0
Extra: 019df075a8d2dea23a1ad1c0e0638d134df4758822481c633f292752e55ce6e63b0208c150856e2eb8c024

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3fcd25b2ad2495eb4b1b7d4397b60eb52f6fd6108954845dfe848a4a2241ae08 0.000600000000 2064097 of 15 <3f>

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": 1574127, "vin": [ { "gen": { "height": 1574117 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "3fcd25b2ad2495eb4b1b7d4397b60eb52f6fd6108954845dfe848a4a2241ae08", "view_tag": "3f" } } } ], "extra": [ 1, 157, 240, 117, 168, 210, 222, 162, 58, 26, 209, 192, 224, 99, 141, 19, 77, 244, 117, 136, 34, 72, 28, 99, 63, 41, 39, 82, 229, 92, 230, 230, 59, 2, 8, 193, 80, 133, 110, 46, 184, 192, 36 ], "rct_signatures": { "type": 0 } }


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