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: e559744795f657ff64d6ba791230cad6d992418c5954ea15690605ad4fee2a6d
Tx prefix hash: fd7305e89dff88e637a3d424e1437881ccab3caa59f266c093cce6ae56bb08fa
Tx public key: ce7c7968a5a323aad481ca22cfc61849061e4192c6fa2026856e9b3ffd20308b
| Timestamp: 1779886179 | Timestamp [UTC]: 2026-05-27 12:49:39 | Age [y:d:h:m:s]: 00:012:12:46:18 |
| Block: 3011 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4875 | RingCT/type: yes/0 |
| Extra: 01ce7c7968a5a323aad481ca22cfc61849061e4192c6fa2026856e9b3ffd20308b02090000000226697be300 | ||
1 output(s) for total of 34.986362155102 HMNY
| stealth address | amount | amount idx | tag |
| 00: 36a8afcb19ecd5bcffe4a314aae8a0b0feef2c6b3fdc0fa2ab32180569afe022 | 34.986362155102 | 3575 of 0 | <0f> |
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": 3071,
"vin": [ {
"gen": {
"height": 3011
}
}
],
"vout": [ {
"amount": 34986362155102,
"target": {
"tagged_key": {
"key": "36a8afcb19ecd5bcffe4a314aae8a0b0feef2c6b3fdc0fa2ab32180569afe022",
"view_tag": "0f"
}
}
}
],
"extra": [ 1, 206, 124, 121, 104, 165, 163, 35, 170, 212, 129, 202, 34, 207, 198, 24, 73, 6, 30, 65, 146, 198, 250, 32, 38, 133, 110, 155, 63, 253, 32, 48, 139, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}