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: 9d47505803340d16114d945881df59640cca0f792846231b011b77d4127d0d2b
Tx prefix hash: 417395395c917a2b62ca570e47ece57c53bd4c0b05f97c052d062c7e600f1b39
Tx public key: 8bdca3c72db5c2068c6879ab6d7ac6f712e0e6081a50314cdc7c035405f6d263
| Timestamp: 1780859333 | Timestamp [UTC]: 2026-06-07 19:08:53 | Age [y:d:h:m:s]: 00:001:03:15:56 |
| Block: 7602 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 284 | RingCT/type: yes/0 |
| Extra: 018bdca3c72db5c2068c6879ab6d7ac6f712e0e6081a50314cdc7c035405f6d263020900000001e49593ff00 | ||
1 output(s) for total of 34.677956942628 HMNY
| stealth address | amount | amount idx | tag |
| 00: 557238e641d1fd7d8f57555b967cdd0ea359c318c388763cee690f3cdda7adc7 | 34.677956942628 | 9392 of 0 | <2e> |
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": 7662,
"vin": [ {
"gen": {
"height": 7602
}
}
],
"vout": [ {
"amount": 34677956942628,
"target": {
"tagged_key": {
"key": "557238e641d1fd7d8f57555b967cdd0ea359c318c388763cee690f3cdda7adc7",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 139, 220, 163, 199, 45, 181, 194, 6, 140, 104, 121, 171, 109, 122, 198, 247, 18, 224, 230, 8, 26, 80, 49, 76, 220, 124, 3, 84, 5, 246, 210, 99, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}