Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f1e5470925bd9252f71a6717769b781c921b573b1e2ef320b2e4f0d51f8b68

Tx prefix hash: 5450bce3a56b9afc95174221063070b48b1047dbcea947df0863663ad62fa106
Tx public key: 218e554ec4dbcf4bcb642e67132ba1d2088a33c965a0fa6461ad2ae856e903c9
Timestamp: 1747001004 Timestamp [UTC]: 2025-05-11 22:03:24 Age [y:d:h:m:s]: 01:100:17:24:11
Block: 1280877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336685 RingCT/type: yes/0
Extra: 01218e554ec4dbcf4bcb642e67132ba1d2088a33c965a0fa6461ad2ae856e903c90211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a14a65ab1e3659ec488199a2b017432db961e1e550e44ad2f6a7a4ee129c7188 0.000600000000 1768270 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": 1280887, "vin": [ { "gen": { "height": 1280877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a14a65ab1e3659ec488199a2b017432db961e1e550e44ad2f6a7a4ee129c7188" } } ], "extra": [ 1, 33, 142, 85, 78, 196, 219, 207, 75, 203, 100, 46, 103, 19, 43, 161, 210, 8, 138, 51, 201, 101, 160, 250, 100, 97, 173, 42, 232, 86, 233, 3, 201, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: