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: 0f16c376b00241612d587ce32495b154a33846943f26fbb3b399c8eba7a1b36e
Tx prefix hash: d50f8f83b43290309b04dbf11291346d9e4ea9117210349cfe938de7a196f67c
Tx public key: 40b0329deaac51d6b05ec69b7799e45ccdbb1df8e49e084c2c80ad49e0c96e77
| Timestamp: 1780687191 | Timestamp [UTC]: 2026-06-05 19:19:51 | Age [y:d:h:m:s]: 00:003:06:16:06 |
| Block: 5464 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2422 | RingCT/type: yes/0 |
| Extra: 0140b0329deaac51d6b05ec69b7799e45ccdbb1df8e49e084c2c80ad49e0c96e77020900000001e49593ff00 | ||
1 output(s) for total of 34.819659441660 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4492971e214d8df8c2fdb41d199d3108df34bfbfde48940146ed0d4f94fa0a04 | 34.819659441660 | 6903 of 0 | <89> |
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": 5524,
"vin": [ {
"gen": {
"height": 5464
}
}
],
"vout": [ {
"amount": 34819659441660,
"target": {
"tagged_key": {
"key": "4492971e214d8df8c2fdb41d199d3108df34bfbfde48940146ed0d4f94fa0a04",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 64, 176, 50, 157, 234, 172, 81, 214, 176, 94, 198, 155, 119, 153, 228, 92, 205, 187, 29, 248, 228, 158, 8, 76, 44, 128, 173, 73, 224, 201, 110, 119, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}