For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: a83be915c070ad7d1e0da5672ba4e1dc7cffbd2a3032d29019dd37777596e39b
Tx prefix hash: ecb0302147ab223784cfb07b04dc857c06a22ab5afd99a1818d723cfab8fb710
Tx public key: ad2a67d188b5a3f6e1ac63f69d9780c1bf3f7c450ee641079301293ee8a0ed4a
| Timestamp: 1780978311 | Timestamp [UTC]: 2026-06-09 04:11:51 | Age [y:d:h:m:s]: 00:000:10:37:04 |
| Block: 7977 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 666 | RingCT/type: yes/0 |
| Extra: 01ad2a67d188b5a3f6e1ac63f69d9780c1bf3f7c450ee641079301293ee8a0ed4a020900000001e49593ff00 | ||
1 output(s) for total of 34.653162179676 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5df0cd6f3574ed4e2d591ebf79e9197f61ccff0c4bdf9fb57633f4e25908fcfe | 34.653162179676 | 9893 of 0 | <2b> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 8037,
"vin": [ {
"gen": {
"height": 7977
}
}
],
"vout": [ {
"amount": 34653162179676,
"target": {
"tagged_key": {
"key": "5df0cd6f3574ed4e2d591ebf79e9197f61ccff0c4bdf9fb57633f4e25908fcfe",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 173, 42, 103, 209, 136, 181, 163, 246, 225, 172, 99, 246, 157, 151, 128, 193, 191, 63, 124, 69, 14, 230, 65, 7, 147, 1, 41, 62, 232, 160, 237, 74, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}