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: fba96ddaf965c6eb6344fa06312788ebb81d53f889f2352483340bf2ed158424
Tx prefix hash: 7fc2802c380c7479562b8202f0e283120c651219eb70c1606ddc2493852f8969
Tx public key: cf0c6894fc29f4a33aac054d8d648bef1caed29c8c64afee8e2bb4fc2e3314d1
| Timestamp: 1780393050 | Timestamp [UTC]: 2026-06-02 09:37:30 | Age [y:d:h:m:s]: 00:006:18:01:20 |
| Block: 5223 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2727 | RingCT/type: yes/0 |
| Extra: 01cf0c6894fc29f4a33aac054d8d648bef1caed29c8c64afee8e2bb4fc2e3314d102090000000126697be300 | ||
1 output(s) for total of 34.835668724536 HMNY
| stealth address | amount | amount idx | tag |
| 00: db96bb15e0d9a1a7a1f3d68bdd9370a0f4c7ba413ba30705c14335d4fe68d572 | 34.835668724536 | 6610 of 0 | <fd> |
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": 5283,
"vin": [ {
"gen": {
"height": 5223
}
}
],
"vout": [ {
"amount": 34835668724536,
"target": {
"tagged_key": {
"key": "db96bb15e0d9a1a7a1f3d68bdd9370a0f4c7ba413ba30705c14335d4fe68d572",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 207, 12, 104, 148, 252, 41, 244, 163, 58, 172, 5, 77, 141, 100, 139, 239, 28, 174, 210, 156, 140, 100, 175, 238, 142, 43, 180, 252, 46, 51, 20, 209, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}