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: 1fdcc99d534d60c02a784e267fc25da5f82cba1031a5d309055ef6243b46a334
Tx prefix hash: 3d5aa96871a5beef60bf33856e1e7de5f4e4531a0879850fdf83c3dd2024da4e
Tx public key: ef5015e0704ac4b3434e2cbbbbe985b86180f2567a3ac7e07a6b33ce86428d5f
| Timestamp: 1780726407 | Timestamp [UTC]: 2026-06-06 06:13:27 | Age [y:d:h:m:s]: 00:002:21:25:23 |
| Block: 6278 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1669 | RingCT/type: yes/0 |
| Extra: 01ef5015e0704ac4b3434e2cbbbbe985b86180f2567a3ac7e07a6b33ce86428d5f020900000002e49593ff00 | ||
1 output(s) for total of 34.765640965963 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a0ce1eaa76414641c1ecb726656e126d721bcc73d182a060888ddbf789ab950 | 34.765640965963 | 7761 of 0 | <84> |
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": 6338,
"vin": [ {
"gen": {
"height": 6278
}
}
],
"vout": [ {
"amount": 34765640965963,
"target": {
"tagged_key": {
"key": "8a0ce1eaa76414641c1ecb726656e126d721bcc73d182a060888ddbf789ab950",
"view_tag": "84"
}
}
}
],
"extra": [ 1, 239, 80, 21, 224, 112, 74, 196, 179, 67, 78, 44, 187, 187, 233, 133, 184, 97, 128, 242, 86, 122, 58, 199, 224, 122, 107, 51, 206, 134, 66, 141, 95, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}