Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b07d1d8d8082620fa0dcdbbad82802dcf034d45c15bc12799a02a53b68f2e6

Tx prefix hash: 445bd27834896bda63dc14b11c874d47a84892df51d10fe0c3b4e3722cb8541a
Tx public key: 1ad2bfe3fee5fd8764d7ebabc7cc17be32f8606fb339dc1ead12dcd9437fa26e
Timestamp: 1750427481 Timestamp [UTC]: 2025-06-20 13:51:21 Age [y:d:h:m:s]: 01:030:07:44:26
Block: 1309086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274028 RingCT/type: yes/0
Extra: 011ad2bfe3fee5fd8764d7ebabc7cc17be32f8606fb339dc1ead12dcd9437fa26e02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 388d72113db7b1f824d1c1e875629cd7eba6fcf14fb82049724d8e494a1efae2 0.000600000000 1796701 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": 1309096, "vin": [ { "gen": { "height": 1309086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "388d72113db7b1f824d1c1e875629cd7eba6fcf14fb82049724d8e494a1efae2" } } ], "extra": [ 1, 26, 210, 191, 227, 254, 229, 253, 135, 100, 215, 235, 171, 199, 204, 23, 190, 50, 248, 96, 111, 179, 57, 220, 30, 173, 18, 220, 217, 67, 127, 162, 110, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: