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: 036ba9864c913040a0f45b91328e909ecad15b631c1ddaf571661fc0e56d0141
Tx prefix hash: 002a4ecc469f4d781eb77872162cfc156c6f2a46dd39b2f2757c61095f9c8f48
Tx public key: fc097af05dacb2c5ffca7595387626f8f6dff895d60a5efdc54e7b9ecf4bdc6c
| Timestamp: 1779954359 | Timestamp [UTC]: 2026-05-28 07:45:59 | Age [y:d:h:m:s]: 00:011:19:52:51 |
| Block: 3667 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4283 | RingCT/type: yes/0 |
| Extra: 01fc097af05dacb2c5ffca7595387626f8f6dff895d60a5efdc54e7b9ecf4bdc6c02090000000526697be300 | ||
1 output(s) for total of 34.939208890837 HMNY
| stealth address | amount | amount idx | tag |
| 00: 918437e83a60960dcfaea74d316d2500cd8e2869f12f95aba455c5cc180e81a5 | 34.939208890837 | 4431 of 0 | <e1> |
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": 3727,
"vin": [ {
"gen": {
"height": 3667
}
}
],
"vout": [ {
"amount": 34939208890837,
"target": {
"tagged_key": {
"key": "918437e83a60960dcfaea74d316d2500cd8e2869f12f95aba455c5cc180e81a5",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 252, 9, 122, 240, 93, 172, 178, 197, 255, 202, 117, 149, 56, 118, 38, 248, 246, 223, 248, 149, 214, 10, 94, 253, 197, 78, 123, 158, 207, 75, 220, 108, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}