Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8111a3575147b57108934c5504e783b0f7b3909bfb16e21f4bca97f4832b0c50

Tx prefix hash: bba4adbee836c6cd7e3d66b4fc411a221f1a6af394995bb8d325f0bd74553eea
Tx public key: 73935f7caf853b4086c0531958a89b3d8a8f12e56df03d020ea0f8a7066c31e7
Timestamp: 1743540001 Timestamp [UTC]: 2025-04-01 20:40:01 Age [y:d:h:m:s]: 01:235:02:30:29
Block: 1252211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431939 RingCT/type: yes/0
Extra: 0173935f7caf853b4086c0531958a89b3d8a8f12e56df03d020ea0f8a7066c31e7021100000005a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a78dd641ab1239d2edb260f52f17c24cb73a1ad7df9e3d207c3307c86a02eb80 0.000600000000 1739290 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": 1252221, "vin": [ { "gen": { "height": 1252211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a78dd641ab1239d2edb260f52f17c24cb73a1ad7df9e3d207c3307c86a02eb80" } } ], "extra": [ 1, 115, 147, 95, 124, 175, 133, 59, 64, 134, 192, 83, 25, 88, 168, 155, 61, 138, 143, 18, 229, 109, 240, 61, 2, 14, 160, 248, 167, 6, 108, 49, 231, 2, 17, 0, 0, 0, 5, 162, 237, 1, 107, 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: