Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb6c4d9990ee9dce6a555661d970abc1d17fe2a5f6cbe539a1daec4d879d6c3

Tx prefix hash: 0c16f64f747f3a6a0637b47bd4d3bfe68c69c250f97953c49ba443aba5a1c077
Tx public key: 1eb1e806495b121a3ff4364df69d5f149b7fcbef08d90303e599ef497920c7b3
Timestamp: 1787621945 Timestamp [UTC]: 2026-08-25 01:39:05 Age [y:d:h:m:s]: 00:089:10:14:33
Block: 1620350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 63144 RingCT/type: yes/0
Extra: 011eb1e806495b121a3ff4364df69d5f149b7fcbef08d90303e599ef497920c7b3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 990afd49d74007b797167d6ed3a72413e88bf1d73084c819db62d32d78d260fe 0.000600000000 2110370 of 15 <26>

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": 1620360, "vin": [ { "gen": { "height": 1620350 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "990afd49d74007b797167d6ed3a72413e88bf1d73084c819db62d32d78d260fe", "view_tag": "26" } } } ], "extra": [ 1, 30, 177, 232, 6, 73, 91, 18, 26, 63, 244, 54, 77, 246, 157, 95, 20, 155, 127, 203, 239, 8, 217, 3, 3, 229, 153, 239, 73, 121, 32, 199, 179 ], "rct_signatures": { "type": 0 } }


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