Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aedbdfd902382c8106e080e11924479c110ee636ad8021b737e3823230c197f3

Tx prefix hash: 98119baa164157e416d3c116e62de35ed74cfdd7382bedc307ba38b2f1a63a3c
Tx public key: 363745ccd69512e641dc4af6b3b39b7d96eb1627329afa0b16de9b1a3b2ae331
Timestamp: 1772000586 Timestamp [UTC]: 2026-02-25 06:23:06 Age [y:d:h:m:s]: 00:268:09:49:01
Block: 1485344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197468 RingCT/type: yes/0
Extra: 01363745ccd69512e641dc4af6b3b39b7d96eb1627329afa0b16de9b1a3b2ae33102110000000af188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e7e469be8460c5988e5cff560a0b73711889cb350f4dc36dcd3d7cc23312c6b5 0.000600000000 1974778 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": 1485354, "vin": [ { "gen": { "height": 1485344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7e469be8460c5988e5cff560a0b73711889cb350f4dc36dcd3d7cc23312c6b5" } } ], "extra": [ 1, 54, 55, 69, 204, 214, 149, 18, 230, 65, 220, 74, 246, 179, 179, 155, 125, 150, 235, 22, 39, 50, 154, 250, 11, 22, 222, 155, 26, 59, 42, 227, 49, 2, 17, 0, 0, 0, 10, 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: