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: b477ec02f6778de5bff5a64a6cdddeba2e96bcf6f659615e9884ca1b93fc53a7
Tx prefix hash: 99d59881648d7a1d1390331e11d9ec29ec946fd3a6c98099ae4fd333b0292c1a
Tx public key: 5c3527a001c6307c22a66e4b1ac73c689e3134fbb9833e810f3a806bc5653329
| Timestamp: 1780986553 | Timestamp [UTC]: 2026-06-09 06:29:13 | Age [y:d:h:m:s]: 00:000:04:57:35 |
| Block: 8153 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 362 | RingCT/type: yes/0 |
| Extra: 015c3527a001c6307c22a66e4b1ac73c689e3134fbb9833e810f3a806bc5653329020900000001e49593ff00 | ||
1 output(s) for total of 34.641531284475 HMNY
| stealth address | amount | amount idx | tag |
| 00: d402574034bd60e9c71544ae1468e4cd259bf6dc69b529763114c471747978bc | 34.641531284475 | 10095 of 0 | <30> |
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": 8213,
"vin": [ {
"gen": {
"height": 8153
}
}
],
"vout": [ {
"amount": 34641531284475,
"target": {
"tagged_key": {
"key": "d402574034bd60e9c71544ae1468e4cd259bf6dc69b529763114c471747978bc",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 92, 53, 39, 160, 1, 198, 48, 124, 34, 166, 110, 75, 26, 199, 60, 104, 158, 49, 52, 251, 185, 131, 62, 129, 15, 58, 128, 107, 197, 101, 51, 41, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}