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: 54c5585555250d0f2ddafda68851fef43d352773d2f834c66fea2606ba457eed
Tx prefix hash: d5d77694b0ff531661e4d2922de7de806c2b114a4760717ae596f0b646269d93
Tx public key: fa4bbd1b665b14b05140d405aff853a29fa14eebbab1f9ccf1ead6c4a12f18ca
| Timestamp: 1780734769 | Timestamp [UTC]: 2026-06-06 08:32:49 | Age [y:d:h:m:s]: 00:002:17:03:08 |
| Block: 6355 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1531 | RingCT/type: yes/0 |
| Extra: 01fa4bbd1b665b14b05140d405aff853a29fa14eebbab1f9ccf1ead6c4a12f18ca020900000001e49593ff00 | ||
1 output(s) for total of 34.760535450788 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5ef757568f5fe2394503b3c7a841b2e72bae881b5956c9630d937e5018cc43a2 | 34.760535450788 | 7842 of 0 | <35> |
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": 6415,
"vin": [ {
"gen": {
"height": 6355
}
}
],
"vout": [ {
"amount": 34760535450788,
"target": {
"tagged_key": {
"key": "5ef757568f5fe2394503b3c7a841b2e72bae881b5956c9630d937e5018cc43a2",
"view_tag": "35"
}
}
}
],
"extra": [ 1, 250, 75, 189, 27, 102, 91, 20, 176, 81, 64, 212, 5, 175, 248, 83, 162, 159, 161, 78, 235, 186, 177, 249, 204, 241, 234, 214, 196, 161, 47, 24, 202, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}