Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e5963a657e6cf44059b24bc3de975e7cbce6cf76deffc3101d81e31e371956c

Tx prefix hash: 99d5aaaedaa5a4db49f0002461f765a88d9dc6a86d6404010411a4956fabd8ef
Tx public key: e313594e3e9500bc84a161823e17b293f37dd3e8734795b69beecba6997f315b
Timestamp: 1744951131 Timestamp [UTC]: 2025-04-18 04:38:51 Age [y:d:h:m:s]: 01:217:20:59:45
Block: 1263903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419591 RingCT/type: yes/0
Extra: 01e313594e3e9500bc84a161823e17b293f37dd3e8734795b69beecba6997f315b021100000003dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0c935abe5b1ce6723757d9e7f084dc0cbe10af9d4e97751891a7016730d8e3a6 0.000600000000 1751096 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": 1263913, "vin": [ { "gen": { "height": 1263903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c935abe5b1ce6723757d9e7f084dc0cbe10af9d4e97751891a7016730d8e3a6" } } ], "extra": [ 1, 227, 19, 89, 78, 62, 149, 0, 188, 132, 161, 97, 130, 62, 23, 178, 147, 243, 125, 211, 232, 115, 71, 149, 182, 155, 238, 203, 166, 153, 127, 49, 91, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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: