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: fa84d8dc19d14684ba59754f10e1af5cc742e6336b33b5a3138c52653c9f5b8f
Tx prefix hash: be71a79a6b08cc95ec25384ca6cb54c9bfeb9cf74a86de52517b426b128d0f9e
Tx public key: 2624beb1ee7de31d39b1895ea59c11e43daaa41a3d09cc8dab4fd136ae9d7c53
| Timestamp: 1780797828 | Timestamp [UTC]: 2026-06-07 02:03:48 | Age [y:d:h:m:s]: 00:001:23:32:09 |
| Block: 6786 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1100 | RingCT/type: yes/0 |
| Extra: 012624beb1ee7de31d39b1895ea59c11e43daaa41a3d09cc8dab4fd136ae9d7c53020900000001e49593ff00 | ||
1 output(s) for total of 34.731971667671 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7e7361a6f2d11d8e8490f033ebe0a542b92f86f2da4b7fd88019d800acc52cc3 | 34.731971667671 | 8380 of 0 | <d3> |
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": 6846,
"vin": [ {
"gen": {
"height": 6786
}
}
],
"vout": [ {
"amount": 34731971667671,
"target": {
"tagged_key": {
"key": "7e7361a6f2d11d8e8490f033ebe0a542b92f86f2da4b7fd88019d800acc52cc3",
"view_tag": "d3"
}
}
}
],
"extra": [ 1, 38, 36, 190, 177, 238, 125, 227, 29, 57, 177, 137, 94, 165, 156, 17, 228, 61, 170, 164, 26, 61, 9, 204, 141, 171, 79, 209, 54, 174, 157, 124, 83, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}