Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74c1e3948f0288383977c1dd4e0fc2d4de6eef6db75c0cc226524cf1a657e06a

Tx prefix hash: ba48efb2c733f2db0b0c20b2d75df2c8de9cdb69564b5a8f0400cc54101fb37e
Tx public key: de78085bc4a77a9d6871a205e7184e8c57cb2a507a83d348eb4b09ecd3ac515b
Timestamp: 1754226129 Timestamp [UTC]: 2025-08-03 13:02:09 Age [y:d:h:m:s]: 01:107:16:19:43
Block: 1339430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342233 RingCT/type: yes/0
Extra: 01de78085bc4a77a9d6871a205e7184e8c57cb2a507a83d348eb4b09ecd3ac515b021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 13db5c6b4d092d639457eea3d7d9e711e1b2699ecd41f96933aa95c22ab34d09 0.000600000000 1827243 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": 1339440, "vin": [ { "gen": { "height": 1339430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13db5c6b4d092d639457eea3d7d9e711e1b2699ecd41f96933aa95c22ab34d09" } } ], "extra": [ 1, 222, 120, 8, 91, 196, 167, 122, 157, 104, 113, 162, 5, 231, 24, 78, 140, 87, 203, 42, 80, 122, 131, 211, 72, 235, 75, 9, 236, 211, 172, 81, 91, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: