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: 42bf74b74eae1ffd90083cf9d4c3bec3e64a6b616c78bc36df81c5817aed9e3f
Tx prefix hash: cde125e7989cba53ad8af9705f905039273e21601ecb08bb75b7ebaa713dd8bf
Tx public key: cda844c44f36d6186db1416f5f699f244925ac90b4c9a4f26e9c0c1ff52776ba
| Timestamp: 1780017118 | Timestamp [UTC]: 2026-05-29 01:11:58 | Age [y:d:h:m:s]: 00:011:01:28:38 |
| Block: 4122 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3774 | RingCT/type: yes/0 |
| Extra: 01cda844c44f36d6186db1416f5f699f244925ac90b4c9a4f26e9c0c1ff52776ba02090000000126697be300 | ||
1 output(s) for total of 34.911515045616 HMNY
| stealth address | amount | amount idx | tag |
| 00: 39672dc2ce3c95aed5111a89d446cc99de28b5b1e31007ab1fe154184de34075 | 34.911515045616 | 5143 of 0 | <da> |
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": 4182,
"vin": [ {
"gen": {
"height": 4122
}
}
],
"vout": [ {
"amount": 34911515045616,
"target": {
"tagged_key": {
"key": "39672dc2ce3c95aed5111a89d446cc99de28b5b1e31007ab1fe154184de34075",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 205, 168, 68, 196, 79, 54, 214, 24, 109, 177, 65, 111, 95, 105, 159, 36, 73, 37, 172, 144, 180, 201, 164, 242, 110, 156, 12, 31, 245, 39, 118, 186, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}