Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 838fef255211a1fde69c73ece2638f9cad3860f5f7325d4cbbc0ee7e373d0bd2

Tx prefix hash: 34448e696416a05482ca13eb4a1ac2ac66d3bdb8f18ff90e9e8194f9665876a5
Tx public key: 9e8e78fa633a36e2450e3628c76cea39d5484e36c67cae18a0320eb062980ce8
Timestamp: 1771481284 Timestamp [UTC]: 2026-02-19 06:08:04 Age [y:d:h:m:s]: 00:273:20:58:39
Block: 1481010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201342 RingCT/type: yes/0
Extra: 019e8e78fa633a36e2450e3628c76cea39d5484e36c67cae18a0320eb062980ce8021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: caa50c482449eeca54f392a108a2b9fc74f32628820e8e84d2eb2b84ae0715ad 0.000600000000 1970384 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": 1481020, "vin": [ { "gen": { "height": 1481010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caa50c482449eeca54f392a108a2b9fc74f32628820e8e84d2eb2b84ae0715ad" } } ], "extra": [ 1, 158, 142, 120, 250, 99, 58, 54, 226, 69, 14, 54, 40, 199, 108, 234, 57, 213, 72, 78, 54, 198, 124, 174, 24, 160, 50, 14, 176, 98, 152, 12, 232, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: