Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f307d1009e4a61e83a6f30b113d14da1f4dcee41a39bfaecb7027704c70e63

Tx prefix hash: 17a298ff602f17e8f1f9a080e9eca391a1f0bb08f4330e150b420a88f296aef3
Tx public key: d0c55116e93b43e6c94eac882e65b106f4b439e49bed04617010a4784b08e780
Timestamp: 1698047427 Timestamp [UTC]: 2023-10-23 07:50:27 Age [y:d:h:m:s]: 03:027:14:55:07
Block: 875770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 805675 RingCT/type: yes/0
Extra: 01d0c55116e93b43e6c94eac882e65b106f4b439e49bed04617010a4784b08e78002110000000dfaf35c9c000000000000000000

1 output(s) for total of 0.000769503252 xmr

stealth address amount amount idx tag
00: 35b7cf0855100fa59a4df2b27bbd5913e99a05e86ddf65ffd75a5ee9d9baa7fd 0.000769503252 1331042 of 0 -

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": 875780, "vin": [ { "gen": { "height": 875770 } } ], "vout": [ { "amount": 769503252, "target": { "key": "35b7cf0855100fa59a4df2b27bbd5913e99a05e86ddf65ffd75a5ee9d9baa7fd" } } ], "extra": [ 1, 208, 197, 81, 22, 233, 59, 67, 230, 201, 78, 172, 136, 46, 101, 177, 6, 244, 180, 57, 228, 155, 237, 4, 97, 112, 16, 164, 120, 75, 8, 231, 128, 2, 17, 0, 0, 0, 13, 250, 243, 92, 156, 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: