Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 533a804a84e2e0597420cc08f243b88e16a5e4382cc81ee36f8e2685c692db84

Tx prefix hash: 6c833535ba1cbd1f2830df9acbcaaba1af79c60bf97ec00e2e1d3ebcf5e612da
Tx public key: 3ffa3f01d8e10f70e7e33b757726c79146510bb5ba5141843bd9dbe8d1048cbf
Timestamp: 1784091693 Timestamp [UTC]: 2026-07-15 05:01:33 Age [y:d:h:m:s]: 00:036:13:36:28
Block: 1582652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 35005 RingCT/type: yes/0
Extra: 013ffa3f01d8e10f70e7e33b757726c79146510bb5ba5141843bd9dbe8d1048cbf0208d44a096e9ac2ebd7

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 665d15f6a5b0e4f4c8ecdeeeffafbb486a4e00b47e230ac4f1e7854461d61ba4 0.000600000000 2072646 of 15 <60>

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": 1582662, "vin": [ { "gen": { "height": 1582652 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "665d15f6a5b0e4f4c8ecdeeeffafbb486a4e00b47e230ac4f1e7854461d61ba4", "view_tag": "60" } } } ], "extra": [ 1, 63, 250, 63, 1, 216, 225, 15, 112, 231, 227, 59, 117, 119, 38, 199, 145, 70, 81, 11, 181, 186, 81, 65, 132, 59, 217, 219, 232, 209, 4, 140, 191, 2, 8, 212, 74, 9, 110, 154, 194, 235, 215 ], "rct_signatures": { "type": 0 } }


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