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: a9f12d1cb3da9edee30179a3bf8340940223845f45b670a3664982bb9965f4c2
Tx prefix hash: 2f220f317345eb34620cf50f3817bbab9c29b272a4888762d36530c5e7c6a8a2
Tx public key: 313634e1dca30e1a8906a1b6f5dd6e2d3889dabeb00a03ac031a2f28c71c3458
| Timestamp: 1780687984 | Timestamp [UTC]: 2026-06-05 19:33:04 | Age [y:d:h:m:s]: 00:003:05:13:43 |
| Block: 5506 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2380 | RingCT/type: yes/0 |
| Extra: 01313634e1dca30e1a8906a1b6f5dd6e2d3889dabeb00a03ac031a2f28c71c3458020900000002e49593ff00 | ||
1 output(s) for total of 34.816870195069 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0e93813d7ba85b3d3f95b831b79a8ce27045ae6b84f755bcda01d69ab7c3329b | 34.816870195069 | 6947 of 0 | <25> |
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": 5566,
"vin": [ {
"gen": {
"height": 5506
}
}
],
"vout": [ {
"amount": 34816870195069,
"target": {
"tagged_key": {
"key": "0e93813d7ba85b3d3f95b831b79a8ce27045ae6b84f755bcda01d69ab7c3329b",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 49, 54, 52, 225, 220, 163, 14, 26, 137, 6, 161, 182, 245, 221, 110, 45, 56, 137, 218, 190, 176, 10, 3, 172, 3, 26, 47, 40, 199, 28, 52, 88, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}