Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d49375a96c8080e70c285c2d74ccfea82db6b66f8f9aee001f419ae5ee579c4e

Tx prefix hash: cf1af0939e791b0ce3f592dd13f62640e516c8790d47f4420c4359cd769ce6f3
Tx public key: df9e20ec74c51904944a89c94c8920db97d3419faa008f2ac56f4821962144a2
Timestamp: 1752948129 Timestamp [UTC]: 2025-07-19 18:02:09 Age [y:d:h:m:s]: 01:001:04:05:25
Block: 1328989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254125 RingCT/type: yes/0
Extra: 01df9e20ec74c51904944a89c94c8920db97d3419faa008f2ac56f4821962144a20211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e51121cefde3e95918aed87f749aa6d8f9c5fc28c9ab286166d456bf5b4ca37a 0.000600000000 1816764 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": 1328999, "vin": [ { "gen": { "height": 1328989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e51121cefde3e95918aed87f749aa6d8f9c5fc28c9ab286166d456bf5b4ca37a" } } ], "extra": [ 1, 223, 158, 32, 236, 116, 197, 25, 4, 148, 74, 137, 201, 76, 137, 32, 219, 151, 211, 65, 159, 170, 0, 143, 42, 197, 111, 72, 33, 150, 33, 68, 162, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: