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: b18308cdd39257f2f301043441a42137cae2c4e313f018b28d8b8bd08697cc6a
Tx prefix hash: be6ba8ae9d4f038a8f6604cc9fe99bf420cef31e9834e7526c7070893ed5c99f
Tx public key: 0310627f85f5064b80dbbbc27247ea359d29d7bed27167b0b81c12db1a5f9c03
| Timestamp: 1780042646 | Timestamp [UTC]: 2026-05-29 08:17:26 | Age [y:d:h:m:s]: 00:010:17:18:31 |
| Block: 4307 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3579 | RingCT/type: yes/0 |
| Extra: 010310627f85f5064b80dbbbc27247ea359d29d7bed27167b0b81c12db1a5f9c0302090000000526697be300 | ||
1 output(s) for total of 34.896584469884 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1300c057b5e0b0be59221f67d1a388f387a493dc5aacffc519fc41975acc5fbc | 34.896584469884 | 5381 of 0 | <86> |
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": 4367,
"vin": [ {
"gen": {
"height": 4307
}
}
],
"vout": [ {
"amount": 34896584469884,
"target": {
"tagged_key": {
"key": "1300c057b5e0b0be59221f67d1a388f387a493dc5aacffc519fc41975acc5fbc",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 3, 16, 98, 127, 133, 245, 6, 75, 128, 219, 187, 194, 114, 71, 234, 53, 157, 41, 215, 190, 210, 113, 103, 176, 184, 28, 18, 219, 26, 95, 156, 3, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}