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: cd9cf6614099e84c9cea2d212e960ba1d6c6cc70adc6de25634debd1326ac960
Tx prefix hash: a251e42a644a23bb011efa6ba71fbe7e71fa7ec6211051a8dbccd1f55b9d3a69
Tx public key: 45534427954236855478a925e8b6b8f9a5c21f15c3e84ac666847a37a867fcd4
| Timestamp: 1779800695 | Timestamp [UTC]: 2026-05-26 13:04:55 | Age [y:d:h:m:s]: 00:013:12:31:02 |
| Block: 2301 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5585 | RingCT/type: yes/0 |
| Extra: 0145534427954236855478a925e8b6b8f9a5c21f15c3e84ac666847a37a867fcd402090000000126697be300 | ||
1 output(s) for total of 35.030359620655 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8e84c4bd770a371cc9bfc37e45302a023586a0b9b0cb300d8c2859d6678f9771 | 35.030359620655 | 2685 of 0 | <89> |
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": 2361,
"vin": [ {
"gen": {
"height": 2301
}
}
],
"vout": [ {
"amount": 35030359620655,
"target": {
"tagged_key": {
"key": "8e84c4bd770a371cc9bfc37e45302a023586a0b9b0cb300d8c2859d6678f9771",
"view_tag": "89"
}
}
}
],
"extra": [ 1, 69, 83, 68, 39, 149, 66, 54, 133, 84, 120, 169, 37, 232, 182, 184, 249, 165, 194, 31, 21, 195, 232, 74, 198, 102, 132, 122, 55, 168, 103, 252, 212, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}