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: b0f91804310dbfa238292e6f3cba85a910326ddeeb252452d9a8e4bcaa65b7f2
Tx prefix hash: 80b0a0a189e2d1924ca773962010fdd2e56aa3255b134f34c00e7ac6fde68e51
Tx public key: 2841722bbf7735d25f0e664b88665a0b43138c714b9339b0ed9bf8e3322fbd86
| Timestamp: 1780983028 | Timestamp [UTC]: 2026-06-09 05:30:28 | Age [y:d:h:m:s]: 00:000:04:39:35 |
| Block: 8081 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 342 | RingCT/type: yes/0 |
| Extra: 012841722bbf7735d25f0e664b88665a0b43138c714b9339b0ed9bf8e3322fbd86020900000001e49593ff00 | ||
1 output(s) for total of 34.646288906053 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9d1a627e22a3430652c12185d62b5289536073801487d191a0b2a99b10415cb3 | 34.646288906053 | 10013 of 0 | <ca> |
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": 8141,
"vin": [ {
"gen": {
"height": 8081
}
}
],
"vout": [ {
"amount": 34646288906053,
"target": {
"tagged_key": {
"key": "9d1a627e22a3430652c12185d62b5289536073801487d191a0b2a99b10415cb3",
"view_tag": "ca"
}
}
}
],
"extra": [ 1, 40, 65, 114, 43, 191, 119, 53, 210, 95, 14, 102, 75, 136, 102, 90, 11, 67, 19, 140, 113, 75, 147, 57, 176, 237, 155, 248, 227, 50, 47, 189, 134, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}