Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90e7ee27e9cb3a80891b5ff9e0839439fe0deb18ddc79d62008901bba9b197bf

Tx prefix hash: 5e94d5a78774cc91e77c7a4b62a71e6f26b06fdbc82c1a33e6bf85a1e1bad710
Tx public key: 35824fe60a13d81627462be3a6f908ba491080dec73699974385fd1f2c8aad68
Timestamp: 1772801349 Timestamp [UTC]: 2026-03-06 12:49:09 Age [y:d:h:m:s]: 00:259:20:28:14
Block: 1491935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191370 RingCT/type: yes/0
Extra: 0135824fe60a13d81627462be3a6f908ba491080dec73699974385fd1f2c8aad68021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 386d1d2d70b2bc2cbc743e3d0f6a40283a00e4144f7b58d05c4dc53a250db0cc 0.000600000000 1981471 of 15 -

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": 1491945, "vin": [ { "gen": { "height": 1491935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "386d1d2d70b2bc2cbc743e3d0f6a40283a00e4144f7b58d05c4dc53a250db0cc" } } ], "extra": [ 1, 53, 130, 79, 230, 10, 19, 216, 22, 39, 70, 43, 227, 166, 249, 8, 186, 73, 16, 128, 222, 199, 54, 153, 151, 67, 133, 253, 31, 44, 138, 173, 104, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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