Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b522e529844a70f89bc61cd006bf2e43cf0c5bc3735d7463f4d94b969136da53

Tx prefix hash: d18efc0a3ff58d28f245396f7d81b31d96e38824dcb691db238192786ff2905a
Tx public key: 0d5332547c11e25c15454dd20bb0576a16368ddcfb673c09a663f996e7dbd2a9
Timestamp: 1782171656 Timestamp [UTC]: 2026-06-22 23:40:56 Age [y:d:h:m:s]: 00:152:17:32:51
Block: 1565784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 117710 RingCT/type: yes/0
Extra: 010d5332547c11e25c15454dd20bb0576a16368ddcfb673c09a663f996e7dbd2a902089e00c4ef68eaadd6

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 12e35bd053266284b88812e58ac07f2ea2dbf0ffc5c4c75fa485e5140d979ce6 0.000600000000 2055764 of 15 <9d>

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": 1565794, "vin": [ { "gen": { "height": 1565784 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "12e35bd053266284b88812e58ac07f2ea2dbf0ffc5c4c75fa485e5140d979ce6", "view_tag": "9d" } } } ], "extra": [ 1, 13, 83, 50, 84, 124, 17, 226, 92, 21, 69, 77, 210, 11, 176, 87, 106, 22, 54, 141, 220, 251, 103, 60, 9, 166, 99, 249, 150, 231, 219, 210, 169, 2, 8, 158, 0, 196, 239, 104, 234, 173, 214 ], "rct_signatures": { "type": 0 } }


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