Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 030eb59e88b7443fbb8ea40f7f610ef3b3c7116e72a7e5c0c48dd0d020d3319f

Tx prefix hash: ad168b7b75283c31bdd23f82f69cecec2aad2c91d0f20638b28cc1c584d168b1
Tx public key: 3d2f09f07290f7d250983d58c768572ea915ef3eebc84ae3c99fb6f912cb5a04
Timestamp: 1789754523 Timestamp [UTC]: 2026-09-18 18:02:03 Age [y:d:h:m:s]: 00:062:16:56:30
Block: 1638351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 44281 RingCT/type: yes/0
Extra: 013d2f09f07290f7d250983d58c768572ea915ef3eebc84ae3c99fb6f912cb5a04

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ebc7d9eb2d44ed0ec5ecb9225b2ba7363435253c6a4b631598b2300e305bf454 0.000600000000 2128381 of 15 <ae>

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": 1638361, "vin": [ { "gen": { "height": 1638351 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "ebc7d9eb2d44ed0ec5ecb9225b2ba7363435253c6a4b631598b2300e305bf454", "view_tag": "ae" } } } ], "extra": [ 1, 61, 47, 9, 240, 114, 144, 247, 210, 80, 152, 61, 88, 199, 104, 87, 46, 169, 21, 239, 62, 235, 200, 74, 227, 201, 159, 182, 249, 18, 203, 90, 4 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: