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: 4549cc8f74506f550741a4624c0fd6f78778d1e5ebf183be62cce3bde6c259d1
Tx prefix hash: bdf00d35271653c4a173fc4ad91c1dbed7e251175dc41dc19685437deb62c639
Tx public key: f53cf04f1806ff496a8d523175c8ffebddca1434ab91de06ba0f07d418981f6e
| Timestamp: 1779946732 | Timestamp [UTC]: 2026-05-28 05:38:52 | Age [y:d:h:m:s]: 00:011:19:07:55 |
| Block: 3569 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4317 | RingCT/type: yes/0 |
| Extra: 01f53cf04f1806ff496a8d523175c8ffebddca1434ab91de06ba0f07d418981f6e02090000000326697be300 | ||
1 output(s) for total of 34.945740350204 HMNY
| stealth address | amount | amount idx | tag |
| 00: 13b8d0ee9462a883ac70ba74d803e43f4b5a417d24ece7f7aa7966ef72b9c817 | 34.945740350204 | 4308 of 0 | <c0> |
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": 3629,
"vin": [ {
"gen": {
"height": 3569
}
}
],
"vout": [ {
"amount": 34945740350204,
"target": {
"tagged_key": {
"key": "13b8d0ee9462a883ac70ba74d803e43f4b5a417d24ece7f7aa7966ef72b9c817",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 245, 60, 240, 79, 24, 6, 255, 73, 106, 141, 82, 49, 117, 200, 255, 235, 221, 202, 20, 52, 171, 145, 222, 6, 186, 15, 7, 212, 24, 152, 31, 110, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}