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: bdd88eceaabdb02cfa365c946e860d4af509d13a21db6d8a3eb23899e9fba9dd
Tx prefix hash: 49d8342094a9fa731495204bd6cb30ce918fefb8bc9300194e999a1e85984f84
Tx public key: d777993ecf47176c0026708a0688d55d4612dbbcfb3b5b9fdeead59550eef4e8
| Timestamp: 1780861438 | Timestamp [UTC]: 2026-06-07 19:43:58 | Age [y:d:h:m:s]: 00:001:02:40:51 |
| Block: 7623 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 263 | RingCT/type: yes/0 |
| Extra: 01d777993ecf47176c0026708a0688d55d4612dbbcfb3b5b9fdeead59550eef4e8020900000001e49593ff00 | ||
1 output(s) for total of 34.676567967092 HMNY
| stealth address | amount | amount idx | tag |
| 00: aa761e88279ec2c81924a36db84444f43df8f6b9395cb7fa4dd2cd8ed409c63c | 34.676567967092 | 9421 of 0 | <f9> |
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": 7683,
"vin": [ {
"gen": {
"height": 7623
}
}
],
"vout": [ {
"amount": 34676567967092,
"target": {
"tagged_key": {
"key": "aa761e88279ec2c81924a36db84444f43df8f6b9395cb7fa4dd2cd8ed409c63c",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 215, 119, 153, 62, 207, 71, 23, 108, 0, 38, 112, 138, 6, 136, 213, 93, 70, 18, 219, 188, 251, 59, 91, 159, 222, 234, 213, 149, 80, 238, 244, 232, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}