Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a05c55102f2f02df7b72e48a15ec092bf5486dc62682b1b333cb87a6c5796e09

Tx prefix hash: eaf144c807860ca8ca59398a254f49c24b9cac309454c3ec0b69b936b4698043
Tx public key: 6a29982aa66146c9d7d673c0041519e41deb0d3cd39307430bb3b671709473b5
Timestamp: 1744185279 Timestamp [UTC]: 2025-04-09 07:54:39 Age [y:d:h:m:s]: 01:038:17:54:46
Block: 1257559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278760 RingCT/type: yes/0
Extra: 016a29982aa66146c9d7d673c0041519e41deb0d3cd39307430bb3b671709473b5021100000005dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f2e0bffe1a2aaf983d16c883d272344cedd68ab8e62e89252c32238bbac9b968 0.000600000000 1744686 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": 1257569, "vin": [ { "gen": { "height": 1257559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2e0bffe1a2aaf983d16c883d272344cedd68ab8e62e89252c32238bbac9b968" } } ], "extra": [ 1, 106, 41, 152, 42, 166, 97, 70, 201, 215, 214, 115, 192, 4, 21, 25, 228, 29, 235, 13, 60, 211, 147, 7, 67, 11, 179, 182, 113, 112, 148, 115, 181, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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: