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: c48f136f46f6210cb732c72ea8603a7186b1620548adb1ca2fc18a543101fea1
Tx prefix hash: 958b5a4c75056330aa79a7c64f6b2df549241f0b0e0e38d855752c3b51ee535f
Tx public key: aa0b8cb0e48b0e7911dacf334e3dbe388e7cac7dc0ad985a577110b9494c02aa
| Timestamp: 1780323277 | Timestamp [UTC]: 2026-06-01 14:14:37 | Age [y:d:h:m:s]: 00:007:11:21:20 |
| Block: 5097 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2789 | RingCT/type: yes/0 |
| Extra: 01aa0b8cb0e48b0e7911dacf334e3dbe388e7cac7dc0ad985a577110b9494c02aa02090000005326697be300 | ||
1 output(s) for total of 34.844041653001 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9a877258999596819c24aaff7c0a67023d9d72abda11d50ac794a491c8aa0a5 | 34.844041653001 | 6472 of 0 | <72> |
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": 5157,
"vin": [ {
"gen": {
"height": 5097
}
}
],
"vout": [ {
"amount": 34844041653001,
"target": {
"tagged_key": {
"key": "d9a877258999596819c24aaff7c0a67023d9d72abda11d50ac794a491c8aa0a5",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 170, 11, 140, 176, 228, 139, 14, 121, 17, 218, 207, 51, 78, 61, 190, 56, 142, 124, 172, 125, 192, 173, 152, 90, 87, 113, 16, 185, 73, 76, 2, 170, 2, 9, 0, 0, 0, 83, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}