Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f1e65b0ef9c0001c3d7e8ee8b3dc313723d6181c4b1542eaa27d840e35d4940

Tx prefix hash: b42bcbb826e9c4616e7ab8a914e2ed0a5b3cd06b03eae157ff8fc4e810e5b5cc
Tx public key: 65a8d8d3da18374c99b32a8d25a4fb4307e1bc3a48987a6f4a435e5d8ddec729
Timestamp: 1794690846 Timestamp [UTC]: 2026-11-14 21:14:06 Age [y:d:h:m:s]: 00:001:12:15:54
Block: 1678404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 1146 RingCT/type: yes/0
Extra: 0165a8d8d3da18374c99b32a8d25a4fb4307e1bc3a48987a6f4a435e5d8ddec729

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 10335b6faf35dd4056abcad1c1ac2a70f924ed156079de509d515e6f62a67d36 0.000600000000 2169166 of 15 <ea>

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": 1678414, "vin": [ { "gen": { "height": 1678404 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "10335b6faf35dd4056abcad1c1ac2a70f924ed156079de509d515e6f62a67d36", "view_tag": "ea" } } } ], "extra": [ 1, 101, 168, 216, 211, 218, 24, 55, 76, 153, 179, 42, 141, 37, 164, 251, 67, 7, 225, 188, 58, 72, 152, 122, 111, 74, 67, 94, 93, 141, 222, 199, 41 ], "rct_signatures": { "type": 0 } }


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