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: ba72bb8bce927d1a911cf714ee907a335c10b95602aac9e8d2991d99e0b010f3
Tx prefix hash: b039dfc9879d1a50b4441f2ee1006ae32729cc83f7f95dbebba9b9dad371ccb0
Tx public key: 2e787e0d40b518441a00b765f39808a2a198fa81afef3aa7ab8e3fb0754faaaf
| Timestamp: 1780688526 | Timestamp [UTC]: 2026-06-05 19:42:06 | Age [y:d:h:m:s]: 00:003:05:53:51 |
| Block: 5532 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2354 | RingCT/type: yes/0 |
| Extra: 012e787e0d40b518441a00b765f39808a2a198fa81afef3aa7ab8e3fb0754faaaf020900000001e49593ff00 | ||
1 output(s) for total of 34.815143630580 HMNY
| stealth address | amount | amount idx | tag |
| 00: cf6cd37a869551723bd5f2966aa2ac8cba6d2499e018030d5fe19d030ed5dc87 | 34.815143630580 | 6975 of 0 | <4e> |
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": 5592,
"vin": [ {
"gen": {
"height": 5532
}
}
],
"vout": [ {
"amount": 34815143630580,
"target": {
"tagged_key": {
"key": "cf6cd37a869551723bd5f2966aa2ac8cba6d2499e018030d5fe19d030ed5dc87",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 46, 120, 126, 13, 64, 181, 24, 68, 26, 0, 183, 101, 243, 152, 8, 162, 161, 152, 250, 129, 175, 239, 58, 167, 171, 142, 63, 176, 117, 79, 170, 175, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}