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: 1728fe4fdf193c76762d0b7a60dda2c941cdc15e415d21aab03c0430ec08da75
Tx prefix hash: ab7eaa520648d5c359f8ef3c1a8339d39d71a85f514084b4fb751d763c3eecf3
Tx public key: 373bc51648423f14a3f9ee32fcb2dfea43d19381a16c1a387de73592259b3e57
| Timestamp: 1780026768 | Timestamp [UTC]: 2026-05-29 03:52:48 | Age [y:d:h:m:s]: 00:015:07:09:28 |
| Block: 4174 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4571 | RingCT/type: yes/0 |
| Extra: 01373bc51648423f14a3f9ee32fcb2dfea43d19381a16c1a387de73592259b3e5702090000000126697be300 | ||
1 output(s) for total of 34.905438074966 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ef539e120c10d512464e30f43ca1237eec07c29af1e737ed15628327139e0b4 | 34.905438074966 | 5207 of 0 | <dd> |
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": 4234,
"vin": [ {
"gen": {
"height": 4174
}
}
],
"vout": [ {
"amount": 34905438074966,
"target": {
"tagged_key": {
"key": "3ef539e120c10d512464e30f43ca1237eec07c29af1e737ed15628327139e0b4",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 55, 59, 197, 22, 72, 66, 63, 20, 163, 249, 238, 50, 252, 178, 223, 234, 67, 209, 147, 129, 161, 108, 26, 56, 125, 231, 53, 146, 37, 155, 62, 87, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}