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: c788f79a189f9116819fe10f4e541f23aefc98fee3bad2071e80ec83d9ec5838
Tx prefix hash: 630fde8f9661e29630f1f945b66ce0f0c1cb22df68f637ba9fa85251ebfa117d
Tx public key: 1f804573632539ea822ecec64086d85b6d5e07609b8fb30d59ffed82e5c5f21a
| Timestamp: 1779964864 | Timestamp [UTC]: 2026-05-28 10:41:04 | Age [y:d:h:m:s]: 00:011:15:59:32 |
| Block: 3794 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4102 | RingCT/type: yes/0 |
| Extra: 011f804573632539ea822ecec64086d85b6d5e07609b8fb30d59ffed82e5c5f21a02090000000226697be300 | ||
1 output(s) for total of 34.930746468705 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5e833d3f10655da27b592a6cdbd6d6236273c67a64fd2f77849c23af11ab6ba6 | 34.930746468705 | 4614 of 0 | <ed> |
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": 3854,
"vin": [ {
"gen": {
"height": 3794
}
}
],
"vout": [ {
"amount": 34930746468705,
"target": {
"tagged_key": {
"key": "5e833d3f10655da27b592a6cdbd6d6236273c67a64fd2f77849c23af11ab6ba6",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 31, 128, 69, 115, 99, 37, 57, 234, 130, 46, 206, 198, 64, 134, 216, 91, 109, 94, 7, 96, 155, 143, 179, 13, 89, 255, 237, 130, 229, 197, 242, 26, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}