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: 91c87372e37f1c85d841c763824b31fee8212a678c181119261fdbbbd580de61
Tx prefix hash: 76fff59cd4a245b8baf3a9c75fe30daad14642ab72f50ec5ff68aa001279a910
Tx public key: a5e904e1210a74229e1bc445a10ed94741c2689fe7bc3f2881a9271891861557
| Timestamp: 1779725301 | Timestamp [UTC]: 2026-05-25 16:08:21 | Age [y:d:h:m:s]: 00:014:08:38:26 |
| Block: 1851 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6035 | RingCT/type: yes/0 |
| Extra: 01a5e904e1210a74229e1bc445a10ed94741c2689fe7bc3f2881a9271891861557020900000001ba6d17be00 | ||
1 output(s) for total of 35.060439355154 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b46de0f981687a5e81aa06ecd24ba968d4ab3a0300c99959a007c91cf12c989 | 35.060439355154 | 2047 of 0 | <ea> |
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": 1911,
"vin": [ {
"gen": {
"height": 1851
}
}
],
"vout": [ {
"amount": 35060439355154,
"target": {
"tagged_key": {
"key": "2b46de0f981687a5e81aa06ecd24ba968d4ab3a0300c99959a007c91cf12c989",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 165, 233, 4, 225, 33, 10, 116, 34, 158, 27, 196, 69, 161, 14, 217, 71, 65, 194, 104, 159, 231, 188, 63, 40, 129, 169, 39, 24, 145, 134, 21, 87, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}