Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d35f710ec805459fd1711eadcab88f8a0f84c2cb574c73eba876e90b10501a6

Tx prefix hash: 40c0dd1a5c52d92a8cf1350ae5c7d289a32cd61aa3d63704f88f5c98c136192e
Tx public key: 9b9b3af9c034d8361d0cf74b2588d8ef1726fe05f54ea27802c0b45b60c82daa
Timestamp: 1760807086 Timestamp [UTC]: 2025-10-18 17:04:46 Age [y:d:h:m:s]: 01:029:02:56:40
Block: 1392771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287102 RingCT/type: yes/0
Extra: 019b9b3af9c034d8361d0cf74b2588d8ef1726fe05f54ea27802c0b45b60c82daa021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e13c83f3cfa912d13dbdf65be8eb7d55a823ea37428bd9ecef6849b4d59ebed9 0.000600000000 1881026 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": 1392781, "vin": [ { "gen": { "height": 1392771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e13c83f3cfa912d13dbdf65be8eb7d55a823ea37428bd9ecef6849b4d59ebed9" } } ], "extra": [ 1, 155, 155, 58, 249, 192, 52, 216, 54, 29, 12, 247, 75, 37, 136, 216, 239, 23, 38, 254, 5, 245, 78, 162, 120, 2, 192, 180, 91, 96, 200, 45, 170, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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: