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: 62b4f6b5ee5f22b0946bf6c6165573bb4f6bc0196524d9480612d02b93cfcb4e
Tx prefix hash: eef6dbb2e42e2505a4b233d03a218d322d8deed5a7c7c461407a0dcd1edcb4fc
Tx public key: ca75b93792801d383c5d43a181bbe25b8c8a7e401a622358f052c6d56a15a9e2
| Timestamp: 1780694038 | Timestamp [UTC]: 2026-06-05 21:13:58 | Age [y:d:h:m:s]: 00:007:13:48:18 |
| Block: 5912 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2833 | RingCT/type: yes/0 |
| Extra: 01ca75b93792801d383c5d43a181bbe25b8c8a7e401a622358f052c6d56a15a9e2020900000001e49593ff00 | ||
1 output(s) for total of 34.789918994632 HMNY
| stealth address | amount | amount idx | tag |
| 00: b179d11f4a8cd5a57e88a14920bc92c0e678a05390ee5109f9e4569659964da3 | 34.789918994632 | 7373 of 0 | <44> |
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": 5972,
"vin": [ {
"gen": {
"height": 5912
}
}
],
"vout": [ {
"amount": 34789918994632,
"target": {
"tagged_key": {
"key": "b179d11f4a8cd5a57e88a14920bc92c0e678a05390ee5109f9e4569659964da3",
"view_tag": "44"
}
}
}
],
"extra": [ 1, 202, 117, 185, 55, 146, 128, 29, 56, 60, 93, 67, 161, 129, 187, 226, 91, 140, 138, 126, 64, 26, 98, 35, 88, 240, 82, 198, 213, 106, 21, 169, 226, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}