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: 969d480ac56808bc3788888399eb8cc05937ce354a1d3a45de86ba74a57ed9fc
Tx prefix hash: ed3de37a1deab784b77990684e10811001e698d5d9388c3193b84ab6202852d0
Tx public key: 9576ee4fca90617d2998c3fdd05648d473a53b3a93f6b123a7d2fdc544463ff4
| Timestamp: 1780985621 | Timestamp [UTC]: 2026-06-09 06:13:41 | Age [y:d:h:m:s]: 00:000:09:46:03 |
| Block: 8136 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 556 | RingCT/type: yes/0 |
| Extra: 019576ee4fca90617d2998c3fdd05648d473a53b3a93f6b123a7d2fdc544463ff4020900000002e49593ff00 | ||
1 output(s) for total of 34.642654552872 HMNY
| stealth address | amount | amount idx | tag |
| 00: 796d2b5b851dc24ac831ceac07c5010bcd271b8436618f7857dee2ae3398a5b6 | 34.642654552872 | 10076 of 0 | <67> |
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": 8196,
"vin": [ {
"gen": {
"height": 8136
}
}
],
"vout": [ {
"amount": 34642654552872,
"target": {
"tagged_key": {
"key": "796d2b5b851dc24ac831ceac07c5010bcd271b8436618f7857dee2ae3398a5b6",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 149, 118, 238, 79, 202, 144, 97, 125, 41, 152, 195, 253, 208, 86, 72, 212, 115, 165, 59, 58, 147, 246, 177, 35, 167, 210, 253, 197, 68, 70, 63, 244, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}