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: 2ebb4ce11018c830c70d24c5156567d3c0a146721efc4b744c51837c17ac909e
Tx prefix hash: 8ca7353f3433e57dd73482b459318b2c470bbedfc07b7325071bad6d10c95fec
Tx public key: 6c271a0b787d350ac95a954140b44fdae3291de8d6d4e76746d6ae4afe442db1
| Timestamp: 1780696562 | Timestamp [UTC]: 2026-06-05 21:56:02 | Age [y:d:h:m:s]: 00:003:05:54:56 |
| Block: 5990 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1961 | RingCT/type: yes/0 |
| Extra: 016c271a0b787d350ac95a954140b44fdae3291de8d6d4e76746d6ae4afe442db1020900000001e49593ff00 | ||
1 output(s) for total of 34.784743567343 HMNY
| stealth address | amount | amount idx | tag |
| 00: c1f355b4f482edb0c6594c6344891fc32befca6dd9802a006b40f60fb9f72f91 | 34.784743567343 | 7455 of 0 | <d1> |
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": 6050,
"vin": [ {
"gen": {
"height": 5990
}
}
],
"vout": [ {
"amount": 34784743567343,
"target": {
"tagged_key": {
"key": "c1f355b4f482edb0c6594c6344891fc32befca6dd9802a006b40f60fb9f72f91",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 108, 39, 26, 11, 120, 125, 53, 10, 201, 90, 149, 65, 64, 180, 79, 218, 227, 41, 29, 232, 214, 212, 231, 103, 70, 214, 174, 74, 254, 68, 45, 177, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}