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: 0a6d132f6e774beb17c418b15fd9ed1e5ca278e8ab101ce74b9e12dcc7b4c32f
Tx prefix hash: 9423d5fb5f42e1e9dfb5030c88dfa0e838abccfc4b5237bd20d374efe3aeda5b
Tx public key: df7a64c4600fe4c9fc08085d2a622914b9e640404e0a7760cf5f97df2ed5478c
| Timestamp: 1779473987 | Timestamp [UTC]: 2026-05-22 18:19:47 | Age [y:d:h:m:s]: 00:017:07:16:10 |
| Block: 597 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7289 | RingCT/type: yes/0 |
| Extra: 01df7a64c4600fe4c9fc08085d2a622914b9e640404e0a7760cf5f97df2ed5478c02090000000c93369e7d00 | ||
1 output(s) for total of 35.144397893112 HMNY
| stealth address | amount | amount idx | tag |
| 00: bd4ee28a53df6f8ce0cf0ad290d2bd521e1d4e5953026d4eabf0007398da9d6c | 35.144397893112 | 611 of 0 | <8c> |
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": 657,
"vin": [ {
"gen": {
"height": 597
}
}
],
"vout": [ {
"amount": 35144397893112,
"target": {
"tagged_key": {
"key": "bd4ee28a53df6f8ce0cf0ad290d2bd521e1d4e5953026d4eabf0007398da9d6c",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 223, 122, 100, 196, 96, 15, 228, 201, 252, 8, 8, 93, 42, 98, 41, 20, 185, 230, 64, 64, 78, 10, 119, 96, 207, 95, 151, 223, 46, 213, 71, 140, 2, 9, 0, 0, 0, 12, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}