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: 364b3d924c14b097cdf0ce745505bb54d0a396dd6cb92db62b934181f269f1f0
Tx prefix hash: 51fadf11fcd42036ee862b94ce6c55a570d24f50f1e29273ce0fcd35dd754b0d
Tx public key: 8041ee1d087b63409467999f754e3204187f4219c45c664e8fba3ffb3af30c54
| Timestamp: 1780763135 | Timestamp [UTC]: 2026-06-06 16:25:35 | Age [y:d:h:m:s]: 00:002:06:53:18 |
| Block: 6592 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1294 | RingCT/type: yes/0 |
| Extra: 018041ee1d087b63409467999f754e3204187f4219c45c664e8fba3ffb3af30c54020900000001e49593ff00 | ||
1 output(s) for total of 34.744825777822 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc03e2639273e93864a56cb75423317b5a028b22f3f39d036ab213b061e2d12c | 34.744825777822 | 8120 of 0 | <f5> |
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": 6652,
"vin": [ {
"gen": {
"height": 6592
}
}
],
"vout": [ {
"amount": 34744825777822,
"target": {
"tagged_key": {
"key": "fc03e2639273e93864a56cb75423317b5a028b22f3f39d036ab213b061e2d12c",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 128, 65, 238, 29, 8, 123, 99, 64, 148, 103, 153, 159, 117, 78, 50, 4, 24, 127, 66, 25, 196, 92, 102, 78, 143, 186, 63, 251, 58, 243, 12, 84, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}