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: a95f6581a17884b3f53c4fc3d9cfba624a027c03b09e28040ab60d9a4d3cfc1a
Tx prefix hash: 2a0c957e9dfced18bbca5266d88d459c838ef45704ec8399472bdfd19273972d
Tx public key: 1bd5ba96d86d7285b89fa13e790cbde32167069f067321eb154c65ba87a278ef
| Timestamp: 1779894329 | Timestamp [UTC]: 2026-05-27 15:05:29 | Age [y:d:h:m:s]: 00:012:10:30:28 |
| Block: 3087 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4799 | RingCT/type: yes/0 |
| Extra: 011bd5ba96d86d7285b89fa13e790cbde32167069f067321eb154c65ba87a278ef02090000000126697be300 | ||
1 output(s) for total of 34.977882241547 HMNY
| stealth address | amount | amount idx | tag |
| 00: 932566b46390659f160e7d1e9a0296bacb208a560a18cc0eace9f2290786499c | 34.977882241547 | 3679 of 0 | <d1> |
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": 3147,
"vin": [ {
"gen": {
"height": 3087
}
}
],
"vout": [ {
"amount": 34977882241547,
"target": {
"tagged_key": {
"key": "932566b46390659f160e7d1e9a0296bacb208a560a18cc0eace9f2290786499c",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 27, 213, 186, 150, 216, 109, 114, 133, 184, 159, 161, 62, 121, 12, 189, 227, 33, 103, 6, 159, 6, 115, 33, 235, 21, 76, 101, 186, 135, 162, 120, 239, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}