Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea9b7005531fc4508b264c8e8b9b7d3994def8636699c4b554d7e16e8403981

Tx prefix hash: a7d5ca30a0ba69bc3593e477550b93e69370fa1c34212dc45a4e3bae6ef4e115
Tx public key: 8f55baa4b66dc16c0ef08a027ce9ad8a9c3c7a5b2f472170e02b72d6cb7df68d
Timestamp: 1764392132 Timestamp [UTC]: 2025-11-29 04:55:32 Age [y:d:h:m:s]: 00:355:22:43:48
Block: 1422467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259906 RingCT/type: yes/0
Extra: 018f55baa4b66dc16c0ef08a027ce9ad8a9c3c7a5b2f472170e02b72d6cb7df68d021100000002da554848000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 32af42987be98e3a2c0cdccfd4307d279e7a63b624168edffcc63f13dc50987a 0.000600000000 1911032 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": 1422477, "vin": [ { "gen": { "height": 1422467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32af42987be98e3a2c0cdccfd4307d279e7a63b624168edffcc63f13dc50987a" } } ], "extra": [ 1, 143, 85, 186, 164, 182, 109, 193, 108, 14, 240, 138, 2, 124, 233, 173, 138, 156, 60, 122, 91, 47, 71, 33, 112, 224, 43, 114, 214, 203, 125, 246, 141, 2, 17, 0, 0, 0, 2, 218, 85, 72, 72, 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: