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: 68bba0d66efe2a3e1dd309be3e1c9ec3772854774016c3e2b95ece20724b2e6d
Tx prefix hash: ca66e6729a6f99706152f957d5255ead10d78a632344480a770a2ee9533dabb1
Tx public key: 5eb86b704c3317460e14d2c4415b872f455129efbb59eca30df8ee5a16291b33
| Timestamp: 1780996604 | Timestamp [UTC]: 2026-06-09 09:16:44 | Age [y:d:h:m:s]: 00:000:05:32:11 |
| Block: 8354 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 300 | RingCT/type: yes/0 |
| Extra: 015eb86b704c3317460e14d2c4415b872f455129efbb59eca30df8ee5a16291b33020900000001e49593ff00 | ||
1 output(s) for total of 34.628253048316 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe9d48889e9e83ad7fc4b39e1bd85df53442b45f265aac5870fa5d6a2438bb82 | 34.628253048316 | 10330 of 0 | <8b> |
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": 8414,
"vin": [ {
"gen": {
"height": 8354
}
}
],
"vout": [ {
"amount": 34628253048316,
"target": {
"tagged_key": {
"key": "fe9d48889e9e83ad7fc4b39e1bd85df53442b45f265aac5870fa5d6a2438bb82",
"view_tag": "8b"
}
}
}
],
"extra": [ 1, 94, 184, 107, 112, 76, 51, 23, 70, 14, 20, 210, 196, 65, 91, 135, 47, 69, 81, 41, 239, 187, 89, 236, 163, 13, 248, 238, 90, 22, 41, 27, 51, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}