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: d668077960684da5fb8ead4f428e894a2fba4c9eaf28288bea3e3ad1364fd47e
Tx prefix hash: 0c001976e35bc8a07369de379e9bba1f57fcecb6ac65a8ee4e2e359a5d35db14
Tx public key: 21604c4ec1fdaf5b3734f436769cfbd52354e0ad65e9309e957b1b670b438663
| Timestamp: 1780695485 | Timestamp [UTC]: 2026-06-05 21:38:05 | Age [y:d:h:m:s]: 00:003:03:57:52 |
| Block: 5975 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1911 | RingCT/type: yes/0 |
| Extra: 0121604c4ec1fdaf5b3734f436769cfbd52354e0ad65e9309e957b1b670b438663020900000002e49593ff00 | ||
1 output(s) for total of 34.785738782025 HMNY
| stealth address | amount | amount idx | tag |
| 00: 03090435ae84e16929edc639d5b8d9262116a36ec5ea3ed9c1bdb224c70ef8a4 | 34.785738782025 | 7440 of 0 | <a6> |
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": 6035,
"vin": [ {
"gen": {
"height": 5975
}
}
],
"vout": [ {
"amount": 34785738782025,
"target": {
"tagged_key": {
"key": "03090435ae84e16929edc639d5b8d9262116a36ec5ea3ed9c1bdb224c70ef8a4",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 33, 96, 76, 78, 193, 253, 175, 91, 55, 52, 244, 54, 118, 156, 251, 213, 35, 84, 224, 173, 101, 233, 48, 158, 149, 123, 27, 103, 11, 67, 134, 99, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}