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: 926f821362d48a4e1a65eea4496dd47071caf751f9b1445a8f2269d2c2599069
Tx prefix hash: 0018a1bbf1720b1c3a1b39942e5c99de68499aeb4bb35084b926206d43c9cee4
Tx public key: 3cc5de401f1d8efaa73e343a8303aa9384d8392c0b4afbe90acae928aff1056e
| Timestamp: 1780052255 | Timestamp [UTC]: 2026-05-29 10:57:35 | Age [y:d:h:m:s]: 00:010:14:38:22 |
| Block: 4412 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3474 | RingCT/type: yes/0 |
| Extra: 013cc5de401f1d8efaa73e343a8303aa9384d8392c0b4afbe90acae928aff1056e02090000000126697be300 | ||
1 output(s) for total of 34.889596367971 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8fbf14b000b2f81f47f1325561e618c8d54ab629c3a1c9e7da50b0fe6f7e7c7c | 34.889596367971 | 5520 of 0 | <43> |
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": 4472,
"vin": [ {
"gen": {
"height": 4412
}
}
],
"vout": [ {
"amount": 34889596367971,
"target": {
"tagged_key": {
"key": "8fbf14b000b2f81f47f1325561e618c8d54ab629c3a1c9e7da50b0fe6f7e7c7c",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 60, 197, 222, 64, 31, 29, 142, 250, 167, 62, 52, 58, 131, 3, 170, 147, 132, 216, 57, 44, 11, 74, 251, 233, 10, 202, 233, 40, 175, 241, 5, 110, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}