Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2cf44508f0b07dd4b6931357d7ad9c8753b3acf6d12fbd55a0e2fc7b50271cd

Tx prefix hash: 5a241c178e9df188ca92375c51e7ba45f42b64ddac05bfa31bc5cf4eb9d670e9
Tx public key: 6ada2d425d8e346183f272f7f18278169967d1750c2d205cef6a565401bb919c
Timestamp: 1748011318 Timestamp [UTC]: 2025-05-23 14:41:58 Age [y:d:h:m:s]: 01:181:14:09:29
Block: 1289246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393931 RingCT/type: yes/0
Extra: 016ada2d425d8e346183f272f7f18278169967d1750c2d205cef6a565401bb919c0211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f53d6193afb473733714ee8d846f7aa3566a0d4d4e3f60059c8e7e16e69ebf86 0.000600000000 1776713 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": 1289256, "vin": [ { "gen": { "height": 1289246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f53d6193afb473733714ee8d846f7aa3566a0d4d4e3f60059c8e7e16e69ebf86" } } ], "extra": [ 1, 106, 218, 45, 66, 93, 142, 52, 97, 131, 242, 114, 247, 241, 130, 120, 22, 153, 103, 209, 117, 12, 45, 32, 92, 239, 106, 86, 84, 1, 187, 145, 156, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: