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: f15932b16528120ac9f4344a2026866ca6ab33916faafa788d22fbd4e9c5a3db
Tx prefix hash: f29670b62ed3ff25c4100535ec07513d23dff090b7272f5ebfb81de11a77aba9
Tx public key: acb4a0bd42808a2f5d0aaf3a644b8157c47c84c7a6147e1456bfc8472942ec00
| Timestamp: 1779971614 | Timestamp [UTC]: 2026-05-28 12:33:34 | Age [y:d:h:m:s]: 00:011:13:02:23 |
| Block: 3852 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4034 | RingCT/type: yes/0 |
| Extra: 01acb4a0bd42808a2f5d0aaf3a644b8157c47c84c7a6147e1456bfc8472942ec0002090000000526697be300 | ||
1 output(s) for total of 34.926882422288 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8adae9fb3b1a7b42221a2ddf7c21b0a9879432ef4a5747a3386656a8f932bb50 | 34.926882422288 | 4704 of 0 | <29> |
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": 3912,
"vin": [ {
"gen": {
"height": 3852
}
}
],
"vout": [ {
"amount": 34926882422288,
"target": {
"tagged_key": {
"key": "8adae9fb3b1a7b42221a2ddf7c21b0a9879432ef4a5747a3386656a8f932bb50",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 172, 180, 160, 189, 66, 128, 138, 47, 93, 10, 175, 58, 100, 75, 129, 87, 196, 124, 132, 199, 166, 20, 126, 20, 86, 191, 200, 71, 41, 66, 236, 0, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}