Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565cc84fafd4229b9227f9fc51d8bffeb3cc54ce7e66d3a19eb544be5c715a21

Tx prefix hash: 42f61331edbda67ae540b2a3301c7691ddf785e9509dc157c4df265aa435e387
Tx public key: da04c7e54fc5e73d6c897c183eb82e9aa34c0213edc2f36ede850dac1eb50b43
Timestamp: 1641956610 Timestamp [UTC]: 2022-01-12 03:03:30 Age [y:d:h:m:s]: 04:312:00:59:08
Block: 415397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1266223 RingCT/type: yes/0
Extra: 01da04c7e54fc5e73d6c897c183eb82e9aa34c0213edc2f36ede850dac1eb50b430211000000011a5e7f5d000000000000000000

1 output(s) for total of 0.025800606577 xmr

stealth address amount amount idx tag
00: c9cc7a39e6a56d23693c9f599f9daa396d7b3f95035fbc0727eb8c79d236ec19 0.025800606577 821205 of 0 -

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": 415407, "vin": [ { "gen": { "height": 415397 } } ], "vout": [ { "amount": 25800606577, "target": { "key": "c9cc7a39e6a56d23693c9f599f9daa396d7b3f95035fbc0727eb8c79d236ec19" } } ], "extra": [ 1, 218, 4, 199, 229, 79, 197, 231, 61, 108, 137, 124, 24, 62, 184, 46, 154, 163, 76, 2, 19, 237, 194, 243, 110, 222, 133, 13, 172, 30, 181, 11, 67, 2, 17, 0, 0, 0, 1, 26, 94, 127, 93, 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: