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: aee1bc8d67448ddbde248f88f8747fe36311b1890b5fb4a0bd55e0a5ca29833c
Tx prefix hash: 8e0e5bb962d44910c9f4ae6fcc5d367c087335cb9d8b3e1388f6fc7b68f1199f
Tx public key: cde65d14028dd1bb9de2728d33379cd98591d4398d4a449684aaaf666c44f976
| Timestamp: 1779721092 | Timestamp [UTC]: 2026-05-25 14:58:12 | Age [y:d:h:m:s]: 00:014:06:13:55 |
| Block: 1756 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6130 | RingCT/type: yes/0 |
| Extra: 01cde65d14028dd1bb9de2728d33379cd98591d4398d4a449684aaaf666c44f976020900000001ba6d17be00 | ||
1 output(s) for total of 35.066792822516 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ba9d9c3be2502a3004f5e72fbd381bc760c59a884395286537e783294dc36c3 | 35.066792822516 | 1936 of 0 | <7a> |
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": 1816,
"vin": [ {
"gen": {
"height": 1756
}
}
],
"vout": [ {
"amount": 35066792822516,
"target": {
"tagged_key": {
"key": "4ba9d9c3be2502a3004f5e72fbd381bc760c59a884395286537e783294dc36c3",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 205, 230, 93, 20, 2, 141, 209, 187, 157, 226, 114, 141, 51, 55, 156, 217, 133, 145, 212, 57, 141, 74, 68, 150, 132, 170, 175, 102, 108, 68, 249, 118, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}