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: f8426f07073e4de7a4d3faea281ae094fde0937d59b8f7706fe82e197984f440
Tx prefix hash: 41ac6e5a7f1a3b775d5e979cb3ad5e118de2414811f3c6c07281689a9d5e84ec
Tx public key: fbd6256e5af8045f70a0f3dca2cb3a29ef16a820aa3fa6a3f8497cf8570b45e3
| Timestamp: 1780889171 | Timestamp [UTC]: 2026-06-08 03:26:11 | Age [y:d:h:m:s]: 00:000:17:45:56 |
| Block: 7708 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 178 | RingCT/type: yes/0 |
| Extra: 01fbd6256e5af8045f70a0f3dca2cb3a29ef16a820aa3fa6a3f8497cf8570b45e30209000000034a728a4c00 | ||
1 output(s) for total of 34.670946491550 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3dc511c0b91ee7ed53a2302b3bf3bbc4485a8435d8893273dc51f2524c32ad44 | 34.670946491550 | 9538 of 0 | <29> |
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": 7768,
"vin": [ {
"gen": {
"height": 7708
}
}
],
"vout": [ {
"amount": 34670946491550,
"target": {
"tagged_key": {
"key": "3dc511c0b91ee7ed53a2302b3bf3bbc4485a8435d8893273dc51f2524c32ad44",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 251, 214, 37, 110, 90, 248, 4, 95, 112, 160, 243, 220, 162, 203, 58, 41, 239, 22, 168, 32, 170, 63, 166, 163, 248, 73, 124, 248, 87, 11, 69, 227, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}