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: 697576b95bd8c9ac4207f841c89f76d433f4e43801d007972d2eb48ca1f21918
Tx prefix hash: 7091f26a2c14a8387ff58f9c0078718974b42bc620239f90df087b131c9a2e34
Tx public key: f2c5ad76bb1ae46a4e23f9dc7086de05a6b6f2ab7826f95a04551788e38530c0
| Timestamp: 1779847148 | Timestamp [UTC]: 2026-05-27 01:59:08 | Age [y:d:h:m:s]: 00:012:21:19:45 |
| Block: 2476 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5410 | RingCT/type: yes/0 |
| Extra: 01f2c5ad76bb1ae46a4e23f9dc7086de05a6b6f2ab7826f95a04551788e38530c002090000000126697be300 | ||
1 output(s) for total of 35.034841316718 HMNY
| stealth address | amount | amount idx | tag |
| 00: 29c210fc48f0057937433682d9f11fb6cc95450e8907f150a360f0e631c027eb | 35.034841316718 | 2910 of 0 | <cd> |
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": 2536,
"vin": [ {
"gen": {
"height": 2476
}
}
],
"vout": [ {
"amount": 35034841316718,
"target": {
"tagged_key": {
"key": "29c210fc48f0057937433682d9f11fb6cc95450e8907f150a360f0e631c027eb",
"view_tag": "cd"
}
}
}
],
"extra": [ 1, 242, 197, 173, 118, 187, 26, 228, 106, 78, 35, 249, 220, 112, 134, 222, 5, 166, 182, 242, 171, 120, 38, 249, 90, 4, 85, 23, 136, 227, 133, 48, 192, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}