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: 9b7578894a2ac7b6d42ef0d48aa7f5ea86f92b5daf610a077f240e048eb4c258
Tx prefix hash: dfa917abcbe065a891f3bfcf643338cfd4f787a0af48482fe7fb44c1c493dac0
Tx public key: 8c6cd0db305ef38c6030a4a5f264da376257cf028600204bccac413bff20706d
| Timestamp: 1779807456 | Timestamp [UTC]: 2026-05-26 14:57:36 | Age [y:d:h:m:s]: 00:013:10:38:21 |
| Block: 2365 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5521 | RingCT/type: yes/0 |
| Extra: 018c6cd0db305ef38c6030a4a5f264da376257cf028600204bccac413bff20706d02090000000226697be300 | ||
1 output(s) for total of 35.026083710617 HMNY
| stealth address | amount | amount idx | tag |
| 00: 345a8dd5f574a59c89c21f4eaa1786d2ad8b2bc4bc4dbea4a6f9648558d625b5 | 35.026083710617 | 2771 of 0 | <6e> |
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": 2425,
"vin": [ {
"gen": {
"height": 2365
}
}
],
"vout": [ {
"amount": 35026083710617,
"target": {
"tagged_key": {
"key": "345a8dd5f574a59c89c21f4eaa1786d2ad8b2bc4bc4dbea4a6f9648558d625b5",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 140, 108, 208, 219, 48, 94, 243, 140, 96, 48, 164, 165, 242, 100, 218, 55, 98, 87, 207, 2, 134, 0, 32, 75, 204, 172, 65, 59, 255, 32, 112, 109, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}