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: e9f279b01b280137ac48f0eca955ceab6bba924a6d156139d225b0ff6299d154
Tx prefix hash: d81a5bd58aad8b8e91acf52ccf67f5c93f6c5e8c74a55692c003d8c84ad16ea2
Tx public key: 40bad75efa91f925a00c53acec330e22babff960b22caceff9a2169076a26452
| Timestamp: 1779902770 | Timestamp [UTC]: 2026-05-27 17:26:10 | Age [y:d:h:m:s]: 00:012:09:23:38 |
| Block: 3166 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4734 | RingCT/type: yes/0 |
| Extra: 0140bad75efa91f925a00c53acec330e22babff960b22caceff9a2169076a2645202090000000126697be300 | ||
1 output(s) for total of 34.972612147328 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c4e65b56ad0fe1fdb8c1e413fda0fa29abef0d7e3466ad41579c31415d2ba92 | 34.972612147328 | 3786 of 0 | <d5> |
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": 3226,
"vin": [ {
"gen": {
"height": 3166
}
}
],
"vout": [ {
"amount": 34972612147328,
"target": {
"tagged_key": {
"key": "3c4e65b56ad0fe1fdb8c1e413fda0fa29abef0d7e3466ad41579c31415d2ba92",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 64, 186, 215, 94, 250, 145, 249, 37, 160, 12, 83, 172, 236, 51, 14, 34, 186, 191, 249, 96, 178, 44, 172, 239, 249, 162, 22, 144, 118, 162, 100, 82, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}