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: cf80e02acd0b0053d09f781533cd77a70354abeb67f7d2b8d595e240d6217d3e
Tx prefix hash: f9090fb5e3adcc57dd676267d2c5c61700cbef086cc65454b0ec814c2c14b431
Tx public key: da7a7d6e6339ee4af5d2260386567e32c03ec6e5fab167c707bfe3ccbc27b7b5
| Timestamp: 1779629251 | Timestamp [UTC]: 2026-05-24 13:27:31 | Age [y:d:h:m:s]: 00:015:13:13:05 |
| Block: 821 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7075 | RingCT/type: yes/0 |
| Extra: 01da7a7d6e6339ee4af5d2260386567e32c03ec6e5fab167c707bfe3ccbc27b7b5020900000001ba6d17be00 | ||
1 output(s) for total of 35.129385779241 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1414b653b2c7776ea709bbcaaa727fc72c4e2de17c01069a183a71c67c4529a7 | 35.129385779241 | 953 of 0 | <49> |
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": 881,
"vin": [ {
"gen": {
"height": 821
}
}
],
"vout": [ {
"amount": 35129385779241,
"target": {
"tagged_key": {
"key": "1414b653b2c7776ea709bbcaaa727fc72c4e2de17c01069a183a71c67c4529a7",
"view_tag": "49"
}
}
}
],
"extra": [ 1, 218, 122, 125, 110, 99, 57, 238, 74, 245, 210, 38, 3, 134, 86, 126, 50, 192, 62, 198, 229, 250, 177, 103, 199, 7, 191, 227, 204, 188, 39, 183, 181, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}