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: 5087e8a8633e4a00c4ea9ebe418fb3020b1c142f710a4418eceb7be5d7aba06a
Tx prefix hash: 32208b1c58ab09504e5e68ca76911d3a6426aa669e4cc580f214b7b59e1bb25e
Tx public key: 39026528ff1146de96ba0e9103f963b63c9271dfe49f6a3531861e62f4b31d27
| Timestamp: 1780382854 | Timestamp [UTC]: 2026-06-02 06:47:34 | Age [y:d:h:m:s]: 00:006:19:53:02 |
| Block: 5155 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2741 | RingCT/type: yes/0 |
| Extra: 0139026528ff1146de96ba0e9103f963b63c9271dfe49f6a3531861e62f4b31d2702090000000226697be300 | ||
1 output(s) for total of 34.840187197889 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5d4799628d4eb330ad24e84b665f85260f1553d6c88583ce6149a3d3cef864b8 | 34.840187197889 | 6534 of 0 | <16> |
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": 5215,
"vin": [ {
"gen": {
"height": 5155
}
}
],
"vout": [ {
"amount": 34840187197889,
"target": {
"tagged_key": {
"key": "5d4799628d4eb330ad24e84b665f85260f1553d6c88583ce6149a3d3cef864b8",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 57, 2, 101, 40, 255, 17, 70, 222, 150, 186, 14, 145, 3, 249, 99, 182, 60, 146, 113, 223, 228, 159, 106, 53, 49, 134, 30, 98, 244, 179, 29, 39, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}