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: 234fdb4554da6341e6bcb60acd7e44f910cf46429a4e5473d21d1bec6528e3e1
Tx prefix hash: db2af8c7cb49962e221b78fc90ef50bd36a64f343ba2d32699a0b81cedc894c7
Tx public key: 432fbd55719c16cab9fb2c9cf068c2db1a51962fb56ce4dd33095f675175f5d8
| Timestamp: 1780859639 | Timestamp [UTC]: 2026-06-07 19:13:59 | Age [y:d:h:m:s]: 00:001:21:55:04 |
| Block: 7608 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1127 | RingCT/type: yes/0 |
| Extra: 01432fbd55719c16cab9fb2c9cf068c2db1a51962fb56ce4dd33095f675175f5d8020900000001e49593ff00 | ||
1 output(s) for total of 34.677560086798 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9828dc9cc5df2fdf2398aba077eb42f3077f2c45969b8839b2c06c78a71f8b8e | 34.677560086798 | 9400 of 0 | <da> |
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": 7668,
"vin": [ {
"gen": {
"height": 7608
}
}
],
"vout": [ {
"amount": 34677560086798,
"target": {
"tagged_key": {
"key": "9828dc9cc5df2fdf2398aba077eb42f3077f2c45969b8839b2c06c78a71f8b8e",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 67, 47, 189, 85, 113, 156, 22, 202, 185, 251, 44, 156, 240, 104, 194, 219, 26, 81, 150, 47, 181, 108, 228, 221, 51, 9, 95, 103, 81, 117, 245, 216, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}