Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 082ca0f9aa42637745c33e7662252a740c0aab2e496ebadc6da99f66535f2ac7

Tx prefix hash: 6f1eb097f19ec0752174a82784f0a63f3c310855bd92ae2fa8e3536cfae9905f
Tx public key: aa8d3270cf14813e7be693dff5a2f801690bd2a0cec843c1de3a4e83a8dee840
Timestamp: 1784001775 Timestamp [UTC]: 2026-07-14 04:02:55 Age [y:d:h:m:s]: 00:128:06:50:07
Block: 1581844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 99988 RingCT/type: yes/0
Extra: 01aa8d3270cf14813e7be693dff5a2f801690bd2a0cec843c1de3a4e83a8dee84002089141216fc0fcaed9

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a34442db29c9e291762f2b1dac50c20693450eb7d5c0c8ed6fdf1a419a02f77e 0.000600000000 2071836 of 15 <02>

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": 1581854, "vin": [ { "gen": { "height": 1581844 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a34442db29c9e291762f2b1dac50c20693450eb7d5c0c8ed6fdf1a419a02f77e", "view_tag": "02" } } } ], "extra": [ 1, 170, 141, 50, 112, 207, 20, 129, 62, 123, 230, 147, 223, 245, 162, 248, 1, 105, 11, 210, 160, 206, 200, 67, 193, 222, 58, 78, 131, 168, 222, 232, 64, 2, 8, 145, 65, 33, 111, 192, 252, 174, 217 ], "rct_signatures": { "type": 0 } }


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