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: d60719c43553d8cd9b180a806a6b40f97ac8620f8d9e4e829d14b050d8828483
Tx prefix hash: f7ae010a3c3d10b31370949ebcca874fd5c9d9abc9d8eb62a68e6d4e5ebbe183
Tx public key: 8a080a687bd463bb0ed9e1d3e54963532713924dd56e64f0fa08a85694f841f0
| Timestamp: 1779966049 | Timestamp [UTC]: 2026-05-28 11:00:49 | Age [y:d:h:m:s]: 00:011:14:35:08 |
| Block: 3807 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4079 | RingCT/type: yes/0 |
| Extra: 018a080a687bd463bb0ed9e1d3e54963532713924dd56e64f0fa08a85694f841f002090000000c26697be300 | ||
1 output(s) for total of 34.936402352167 HMNY
| stealth address | amount | amount idx | tag |
| 00: 097256616f099d3dda9185286de87dbc45defb5b762dbad8b87e7d4848439b66 | 34.936402352167 | 4630 of 0 | <bb> |
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": 3867,
"vin": [ {
"gen": {
"height": 3807
}
}
],
"vout": [ {
"amount": 34936402352167,
"target": {
"tagged_key": {
"key": "097256616f099d3dda9185286de87dbc45defb5b762dbad8b87e7d4848439b66",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 138, 8, 10, 104, 123, 212, 99, 187, 14, 217, 225, 211, 229, 73, 99, 83, 39, 19, 146, 77, 213, 110, 100, 240, 250, 8, 168, 86, 148, 248, 65, 240, 2, 9, 0, 0, 0, 12, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}