Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 942a8ee41e9f7e8044bdec6a2cf628ae132c4f37dcbd8020cebf2e4d3165ea96

Tx prefix hash: 79432dbc41a9ffb074366e38b0e18b38c07202ef2318dd1246229913338649bf
Tx public key: d405e056b31f3ae590829ec049c5d3266ac4a2cec8dd8ee781d82ebf398b6ffd
Timestamp: 1740429799 Timestamp [UTC]: 2025-02-24 20:43:19 Age [y:d:h:m:s]: 01:263:09:18:20
Block: 1226460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452226 RingCT/type: yes/0
Extra: 01d405e056b31f3ae590829ec049c5d3266ac4a2cec8dd8ee781d82ebf398b6ffd0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 42f821625a3a8958c298543038dca2e16aae4039e2e9b16737282c781e2aa498 0.000600000000 1713331 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": 1226470, "vin": [ { "gen": { "height": 1226460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42f821625a3a8958c298543038dca2e16aae4039e2e9b16737282c781e2aa498" } } ], "extra": [ 1, 212, 5, 224, 86, 179, 31, 58, 229, 144, 130, 158, 192, 73, 197, 211, 38, 106, 196, 162, 206, 200, 221, 142, 231, 129, 216, 46, 191, 57, 139, 111, 253, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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: