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: acc0f21a9e473d289b327ba02608436cb83c6fe7679f81bc3b1934dba5426533
Tx prefix hash: fc5a73a3d554d9471f7b9a96b76c2dfd31204ab4a4f88c9e6db1d83ba4b1d454
Tx public key: 5ae28f78988a639dbdc0e9de0ea2cc54365c68042c97c1935a03be623080f6cc
| Timestamp: 1780718822 | Timestamp [UTC]: 2026-06-06 04:07:02 | Age [y:d:h:m:s]: 00:002:18:17:47 |
| Block: 6220 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1666 | RingCT/type: yes/0 |
| Extra: 015ae28f78988a639dbdc0e9de0ea2cc54365c68042c97c1935a03be623080f6cc020900000001e49593ff00 | ||
1 output(s) for total of 34.769487173843 HMNY
| stealth address | amount | amount idx | tag |
| 00: c7382bc27a372b554b334f2dbd3ac1ba0aa8fc1d0f95a5cc3306b11f44840cb9 | 34.769487173843 | 7699 of 0 | <d4> |
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": 6280,
"vin": [ {
"gen": {
"height": 6220
}
}
],
"vout": [ {
"amount": 34769487173843,
"target": {
"tagged_key": {
"key": "c7382bc27a372b554b334f2dbd3ac1ba0aa8fc1d0f95a5cc3306b11f44840cb9",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 90, 226, 143, 120, 152, 138, 99, 157, 189, 192, 233, 222, 14, 162, 204, 84, 54, 92, 104, 4, 44, 151, 193, 147, 90, 3, 190, 98, 48, 128, 246, 204, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}