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: 1741592601f66a3f0da9671944a73b6f38e747d899579a9bee23325b3bf3f47c
Tx prefix hash: b11f2489b7bc194481686440b896afa91c1f7a7e794669f7b2c3538ecd30adc4
Tx public key: 1e139138f9911da4588d7b7f57bde44a0a95c84927204f60b6f8ea68e117cce8
| Timestamp: 1780891479 | Timestamp [UTC]: 2026-06-08 04:04:39 | Age [y:d:h:m:s]: 00:000:17:07:28 |
| Block: 7729 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 157 | RingCT/type: yes/0 |
| Extra: 011e139138f9911da4588d7b7f57bde44a0a95c84927204f60b6f8ea68e117cce80209000000034a728a4c00 | ||
1 output(s) for total of 34.669557796807 HMNY
| stealth address | amount | amount idx | tag |
| 00: 522a548e517897dbb37b357ec7507efca5ec40eaa5cacba3a043c783f6a4982d | 34.669557796807 | 9567 of 0 | <b4> |
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": 7789,
"vin": [ {
"gen": {
"height": 7729
}
}
],
"vout": [ {
"amount": 34669557796807,
"target": {
"tagged_key": {
"key": "522a548e517897dbb37b357ec7507efca5ec40eaa5cacba3a043c783f6a4982d",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 30, 19, 145, 56, 249, 145, 29, 164, 88, 141, 123, 127, 87, 189, 228, 74, 10, 149, 200, 73, 39, 32, 79, 96, 182, 248, 234, 104, 225, 23, 204, 232, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}