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: 1eb7c75172f02b7f0a639a82591e0ff0350de9904b5edad675aa1737c9dab3f2
Tx prefix hash: 639fcc0aae12c80201fb435baa3c99e4368bef76166044544d77b8d56216bf6b
Tx public key: 5c94ff8b18e23973bc128606c32d3559f46d2d8d0d924475344ded77558f5dce
| Timestamp: 1780989856 | Timestamp [UTC]: 2026-06-09 07:24:16 | Age [y:d:h:m:s]: 00:000:06:13:20 |
| Block: 8205 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 396 | RingCT/type: yes/0 |
| Extra: 015c94ff8b18e23973bc128606c32d3559f46d2d8d0d924475344ded77558f5dce020900000002e49593ff00 | ||
1 output(s) for total of 34.638095630758 HMNY
| stealth address | amount | amount idx | tag |
| 00: 491af26eff7aab07e2fd7d856b2730e3bb739098acd0f976de94f5046a0fffa4 | 34.638095630758 | 10159 of 0 | <32> |
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": 8265,
"vin": [ {
"gen": {
"height": 8205
}
}
],
"vout": [ {
"amount": 34638095630758,
"target": {
"tagged_key": {
"key": "491af26eff7aab07e2fd7d856b2730e3bb739098acd0f976de94f5046a0fffa4",
"view_tag": "32"
}
}
}
],
"extra": [ 1, 92, 148, 255, 139, 24, 226, 57, 115, 188, 18, 134, 6, 195, 45, 53, 89, 244, 109, 45, 141, 13, 146, 68, 117, 52, 77, 237, 119, 85, 143, 93, 206, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}