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: 4603830ef44358a798244b587fd8a61615e1efab5785372803b6764a8bd8121d
Tx prefix hash: 3155e2f336e4c3abdff6f93dd69e4419db95e885a5e7cb255a016b8a4f52cb8f
Tx public key: 414846323cc750ee9189cfecf3ad67709d905ac85ed487054dbf5d89febd9d48
| Timestamp: 1779720065 | Timestamp [UTC]: 2026-05-25 14:41:05 | Age [y:d:h:m:s]: 00:014:13:09:53 |
| Block: 1738 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6229 | RingCT/type: yes/0 |
| Extra: 01414846323cc750ee9189cfecf3ad67709d905ac85ed487054dbf5d89febd9d48020900000002ba6d17be00 | ||
1 output(s) for total of 35.067996767119 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84b862a180e45b889e43b927881518f67bbc22973659cad9933bbb9974c7a8f4 | 35.067996767119 | 1916 of 0 | <eb> |
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": 1798,
"vin": [ {
"gen": {
"height": 1738
}
}
],
"vout": [ {
"amount": 35067996767119,
"target": {
"tagged_key": {
"key": "84b862a180e45b889e43b927881518f67bbc22973659cad9933bbb9974c7a8f4",
"view_tag": "eb"
}
}
}
],
"extra": [ 1, 65, 72, 70, 50, 60, 199, 80, 238, 145, 137, 207, 236, 243, 173, 103, 112, 157, 144, 90, 200, 94, 212, 135, 5, 77, 191, 93, 137, 254, 189, 157, 72, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}