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: fdf2e2ea4db7adc8cee7b7954531629fcc93e301516813f80e696fdff69a74c2
Tx prefix hash: 6528ee41b63a4a1000aa638abfd9d0c957db955ea2a8f16be2c2332c3f0ead29
Tx public key: 26985ed5e388d16e945a37c0ec3bf3f0628b712a891e94b6f4b947358cb784a3
| Timestamp: 1780038490 | Timestamp [UTC]: 2026-05-29 07:08:10 | Age [y:d:h:m:s]: 00:015:03:54:06 |
| Block: 4261 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4484 | RingCT/type: yes/0 |
| Extra: 0126985ed5e388d16e945a37c0ec3bf3f0628b712a891e94b6f4b947358cb784a302090000000626697be300 | ||
1 output(s) for total of 34.899646364948 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c838604354114ae2a0a14f7c156cec7e1640447de1de62ac1556910bb7dfbca | 34.899646364948 | 5320 of 0 | <fa> |
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": 4321,
"vin": [ {
"gen": {
"height": 4261
}
}
],
"vout": [ {
"amount": 34899646364948,
"target": {
"tagged_key": {
"key": "0c838604354114ae2a0a14f7c156cec7e1640447de1de62ac1556910bb7dfbca",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 38, 152, 94, 213, 227, 136, 209, 110, 148, 90, 55, 192, 236, 59, 243, 240, 98, 139, 113, 42, 137, 30, 148, 182, 244, 185, 71, 53, 140, 183, 132, 163, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}