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: 4746618922ad84e46a29657523f9d84629ae67a49bcfb604e97bffdeb713fc6d
Tx prefix hash: 848589238e05410409d95dfb0a7f4dd9dd8ee9ccfb54bb281eb703c9043b65e7
Tx public key: 6acc4fcea420e70d48b322ef2a032ebb1ff3459bad86a5e6c5b94d91ca8f55ac
| Timestamp: 1780701914 | Timestamp [UTC]: 2026-06-05 23:25:14 | Age [y:d:h:m:s]: 00:003:02:10:43 |
| Block: 6068 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1818 | RingCT/type: yes/0 |
| Extra: 016acc4fcea420e70d48b322ef2a032ebb1ff3459bad86a5e6c5b94d91ca8f55ac020900000001e49593ff00 | ||
1 output(s) for total of 34.779568909962 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe71bb6217795a80aaf545e8f2ab12db3577961272ed42d438dd5762ef162499 | 34.779568909962 | 7539 of 0 | <f0> |
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": 6128,
"vin": [ {
"gen": {
"height": 6068
}
}
],
"vout": [ {
"amount": 34779568909962,
"target": {
"tagged_key": {
"key": "fe71bb6217795a80aaf545e8f2ab12db3577961272ed42d438dd5762ef162499",
"view_tag": "f0"
}
}
}
],
"extra": [ 1, 106, 204, 79, 206, 164, 32, 231, 13, 72, 179, 34, 239, 42, 3, 46, 187, 31, 243, 69, 155, 173, 134, 165, 230, 197, 185, 77, 145, 202, 143, 85, 172, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}