Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398c85d5b55f6555e36c10352824e8b9d00cf7204a6784ce9eeae23298d26c8d

Tx prefix hash: 61421df370e627cad691b51cdebcee156545ec9972439aad39a05ab09a577f11
Tx public key: 4223131e26646bbb9f86e42cca6b32a75f7643fa69273b5c0eabe6fbe1ce6c48
Timestamp: 1741888612 Timestamp [UTC]: 2025-03-13 17:56:52 Age [y:d:h:m:s]: 01:252:00:06:27
Block: 1238567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444290 RingCT/type: yes/0
Extra: 014223131e26646bbb9f86e42cca6b32a75f7643fa69273b5c0eabe6fbe1ce6c48021100000013007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 07b36707e6f921f903e66f3cb9e85a9eb969e49e4debce1a0507916830a59b82 0.000600000000 1725526 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": 1238577, "vin": [ { "gen": { "height": 1238567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07b36707e6f921f903e66f3cb9e85a9eb969e49e4debce1a0507916830a59b82" } } ], "extra": [ 1, 66, 35, 19, 30, 38, 100, 107, 187, 159, 134, 228, 44, 202, 107, 50, 167, 95, 118, 67, 250, 105, 39, 59, 92, 14, 171, 230, 251, 225, 206, 108, 72, 2, 17, 0, 0, 0, 19, 0, 127, 151, 138, 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: