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: b2ef271bd64ac49547a4546ea1c1c2452a7afa634b4800f12c05d84f6eca22af
Tx prefix hash: 2b3578a12bd699892a4fca74c78d8dc2ea8f2d3e12fa30bb2674eaf9c8d1d552
Tx public key: e4de0fb2a18bc75265cecba448bbd15bfcc6b67a3ee22baf3fd974cbc67bd816
| Timestamp: 1779720132 | Timestamp [UTC]: 2026-05-25 14:42:12 | Age [y:d:h:m:s]: 00:014:10:53:45 |
| Block: 1743 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6143 | RingCT/type: yes/0 |
| Extra: 01e4de0fb2a18bc75265cecba448bbd15bfcc6b67a3ee22baf3fd974cbc67bd816020900000003ba6d17be00 | ||
1 output(s) for total of 35.067662333917 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7b1e9cdd8550db9cfc4c562ab646716f4f13bc0e4e8da2107351495c3bfef667 | 35.067662333917 | 1921 of 0 | <78> |
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": 1803,
"vin": [ {
"gen": {
"height": 1743
}
}
],
"vout": [ {
"amount": 35067662333917,
"target": {
"tagged_key": {
"key": "7b1e9cdd8550db9cfc4c562ab646716f4f13bc0e4e8da2107351495c3bfef667",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 228, 222, 15, 178, 161, 139, 199, 82, 101, 206, 203, 164, 72, 187, 209, 91, 252, 198, 182, 122, 62, 226, 43, 175, 63, 217, 116, 203, 198, 123, 216, 22, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}